Hi Felipe, if Zope is started as root, it switches to uid "nobody". Thus preventing access to its directory or at least Zope cannot write over its pid file and such. You may get appropriate messages in your logfile or output (if not sent to /dev/null of course) So all you have to do is to start Zope with the appropriate user-id. see "man su" for this. Regards Tino Wildenhain "Felipe E. Barousse" wrote:
I do believe this approach will work to restart crashed Zope but, I would expect Zope to work correctly and be very stable when it is started from one of the rc startup scripts.
Well, at least it is a way to keep the system kind of working with "minimal" downtime.......
My original idea was to put the start script as an inittab entry. Also I got a respone referencing some other utilities to keep Zope "alive" (i.e. restart it if crashed)
Maybe any of the Zope developers people can give us some illumination as to know what may be happening with this phenomenom of crashing Zope if started at boot time.