Hi Bruce, Well, in OUR setup, Zope uses port 80 directly which is inside the protected range, requiring Medusa and ZServer to run as root. BUT, should you have a normal setup, you can change the line: start() { # Check if atd is already running echo -n $"Starting $prog: " /var/Zope-233b/start RETVAL=$? [ $RETVAL -eq 0 ] echo return $RETVAL to use the SU command, something like: start() { # Check if atd is already running echo -n $"Starting $prog: " su -l zopeown '/var/Zope-233b/start' RETVAL=$? [ $RETVAL -eq 0 ] echo return $RETVAL We've done this before, but I forget the exact syntax of su to provide that it is a shell command, and run as user.... Paz -----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Bruce Tong Sent: Wednesday, July 11, 2001 4:28 PM To: Zope Subject: RE: [Zope] I'm stuck getting Zope to start on boot RH7 Doesn't that modified atd init script run Zope as root? If so, I think that causes problems with some installations. It's been some time since I installed Zope, so I might be forgetting something. I think you might have to get the script to su to the zope user with some installs. There are other Red Hat init scripts which do this. I believe if you do a search on the zope site somebody previously posted an example of an init script which covered this. -- Bruce Tong | Got me an office; I'm there late at night. Sr. Software Engineer | Just send me e-mail, maybe I'll write. Electronic Vision / FITNE | zztong@pugsly.ev.net | -- Joe Walsh for the 21st Century _______________________________________________ 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 )