[Zope] Keeping Zope Alive

[cyrille]

Mike Renfro a =E9crit:
> On Fri, Jan 03, 2003 at 04:24:43AM -0400, beno wrote:
>=20
>=20
>>I seem to have run into this problem before but I don't remember how to=
 fix=20
>>it. I start my Zope with:
>>./start -u www &
>>but it doesn't go into a background process. When I close the shell (or=
=20
>>lose my Internet connection) Zope crashes (2.6.x, RH7.2). What to do?
>=20
>=20
> man nohup
>=20

I think nohup is not the answer :

`nohup': Run a command immune to hangups
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

    `nohup' runs the given COMMAND with hangup signals ignored, so that
the command can continue running in the background after you log out.
Synopsis:

      nohup COMMAND [ARG]...

    `nohup' increases the scheduling priority of COMMAND by 5, so it has
a slightly smaller change to run.  If standard output is a terminal, it
and standard error are redirected so that they are appended to the file
`nohup.out'; if that cannot be written to, they are appended to the
file `$HOME/nohup.out'.  If that cannot be written to, the command is
not run.

    If `nohup' creates either `nohup.out' or `$HOME/nohup.out', it
creates it with no "group" or "other" access permissions.  It does not
change the permissions if the output file already existed.

    `nohup' does not automatically put the command it runs in the
background; you must do that explicitly, by ending the command line
with an `&'.

    The only options are `--help' and `--version'.  *Note Common
options::.

cyrille