[Zope] Starting ZOPE when you don't have access to the machine

Mike Renfro renfro@tntech.edu
Sun, 27 May 2001 09:38:48 -0500

On Sun, May 27, 2001 at 12:39:04PM +0100, Norman Khine wrote:

> I read in a previous post "somewhere" ;^) that if you start zope on a secure
> shell with ./start & and then close this connection the zope server will
> stop running.

It'll eventually crash (or at least flake) when it tries to write to a
non-existent standard output descriptor. Debug mode, or any products
which have Python print statements in them for debugging purposes,
will cause it.

nohup should fix it, and will most likely save any output in
nohup.out, which will help you track down which product or feature is
spewing out print statements.

Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University -- renfro@tntech.edu