GitLab

XXX Not sure if berkeley still works.

failure of chdir.

signal meanings: rotate_logs_handler() was changing the SIGHUP handler
to rotate the logs!  zdaemon did not do anything wrong. :-)
Fixed by *removing* the signal() call inside the handler -- this is
not needed in modern Unixes.

Also changed setup_signals(): there was a typo in the name SIFXFSZ(!);
and made all the signal conditional on whether the signal module has
that particular signal (e.g. on Windows, a signal module exists, but
it only defines a few signals).

1. Use SIGHUP for restart instead of SIGINT, and use SIGUSR2 to reopen
   the log file instead of SIGHUP.  This is the same standard as for
   the Zope server.

2. When using zdaemon, let zdaemon write its pid to the zeo_pid file;
   when not using zdaemon, write only our own pid to the zeo_pid
   file.  Never write two pids.

days.  At least the script zeostart.py did this, and it was a clone of
ZEO1/start.py except for that added feature.  Our sysadmin desperately
wants that feature.

Get rid of $Id$ in docstring (it's seen rarely in ZEO).
Append a newline to the pid file.

"ZEO Server", use "ZEO/start.py".  There was one (PANIC) log message
that used "z2"; changed that one to "ZEO/start.py" as well.

No log writer that I know of has a reinitialize() function.
zLOG has an initialize() function, but it isn't easy to get at yet.

Add a couple of simple tests that make sure that start.py script
runs.  The tests are meager -- most of the possible arguments are
untested -- and only run on Unix.

XXX Should start still do path munging?

the file limit is exceeded.

I expect this code will become ZEO 1.1.

The trunk now has the same code ZEO 1.0b5 plus a few minor changes.

that allow start.py to recover.

Thanks for Chris Withers for reminding about this.

rely on the ZEO __init__, which relies on fap, to sort things out.

Windows.

location of the start.py script (when it is used).

call: 'func(*args)' to old, python1.5.2: 'apply(func, args)'.

(When working on pre-zope2.4 code, you should avoid developing in an
environemnt where python2 is the default python...)

      - It is no longer necessary to symbolically link cPickle or
        ZServer. ZServer is no longer necessary at all.

      - A Zope-style INSTANCE_HOME and var directory are no longer
        needed.

      - If ZServer *is* available, the medusa monitor server can be
        used in the storage server.

      - An option, -d, was added to facilitate generation of a
        detailed debug log while running in the background.

Rearranged handlers to make them a little less signal dependent.