Are you using the zope start script (presumably in /usr/local/zope/2-1-2) unmodified? "Out of the box" that script enables debugging, with the -D switch. That leaves the console attached, which will cause problems like you describe. Take off that switch, or set the logging environment variable STUPID_LOG_FILE in the script 'start,' with something like 'STUPID_LOG_FILE="$PYTHONHOME/var/<whatever-you-want-to-call-the-logfile>" export STUPID_LOG_FILE' The latter will direct debugging messages to the logfile instead of the console, allowing the console to be detached. Craig Dunigan Web Programmer Esker Software - Extending the Reach of Information mailto:craig.dunigan@esker.com Ph. 608.273.6000 Fax 608.273.8227 http://www.esker.com

-----Original Message----- From: Marc Fischer [mailto:marcbpc@gmx.de] Sent: Wednesday, August 22, 2001 9:30 AM To: Jochen Knuth Cc: zope@zope.org Subject: Re: [Zope] PLEASE HELP: automatic start when system boots

Thanks,

I had to realize, that something is not ok. ... But I found a rescue CD :-)

After creating the simlinks, even only in rc3.d, the bootsequence stops at :

starting zope service: .... and nothing more happens!!!!

Perhabs because of a failure in the script??? If I try it manually with: ./startzope start ... the server runs, but the console hangs too. I have to change the console with Alt-Fx.

Here is the used script again:

#! /bin/sh # # processname: zope2

# Source function library. . /etc/rc.d/init.d/functions

# Get config. . /etc/sysconfig/network

# Check that networking is up. if [ ${NETWORKING} = "no" ] then exit 0 fi

# See how we were called. case "$1" in start) echo -n "Starting Zope2 service: " daemon /usr/local/zope/2-1-2/start ;; stop) echo -n "Stopping Zope2 service: " /usr/local/zope/2-1-2/stop ;; restart|reload) $0 stop $0 start ;; *) echo "Usage: zope {start|stop|restart}" exit 1 esac

exit 0

Marc

...

oops,

Jochen Knuth wrote:

...

add these: ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc3.d/S90zope

only this is useful.

Maybe these are also useful (if you start in runlevel 2 or 4) ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc2.d/S90zope ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc4.d/S90zope ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc2.d/K90zope ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc4.d/K90zope

...

ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc0.d/S90zope ln -s /etc/rc.d/init.d/startzope /etc/rc.d/rc6.d/S90zope

these two are bad, because the runlevels 0 and 6 are used for reboot and shutdown.

Ciao, Jochen

P.s.: working with FreeBSD it's sometimes difficult to remember SysV init. -- -------------------------------------------------- Jochen Knuth WebMaster http://www.ipro.de IPRO GmbH Phone ++49-7152-93330 Steinbeisstr. 6 Fax ++49-7152-933340 71229 Leonberg EMail: J.Knuth@ipro.de

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

-- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )