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.

Note that I'm not sure the pids written to the pidfile always make
sense.

documentation.

commit it to the CVS repository.

using the ZConfig.Interpolation module.

in addition to the loads and stores.

This is still in development.

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.

records (all the broken records I've seen had a zero timestamp).

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

Otherwise, this will just hang trying to connect to a read-only
storage.

Also get rid of the debug=1 argument (it's not used with ZEO 2).

It is now easy to provide a subclass of a class that is
instantiated, by setting the corresponding hook class
variable.  E.g. if you subclass ZEOStorage, you should also
subclass StorageServer and set StorageServer.ZEOStorageClass
to your ZEOStorage subclass.

of small and large stores, to try and trigger bugs in the
parallel-call feature.

Got rid of PackWaitWrapper (since pack now waits by default).

Moved the connection test scaffolding to testConnection.py (new);
moved the openClientStorage() implementation into ConnectionTests.py
since it is not platform dependent.

it is in use by another thread.

__init__.  The hang was in the accept() call.  I don't understand
exactly why, but I suspect it was because we were always reusing
the same port when a trigger was closed and another opened right
away.  Fixed this by cycling over ports [19950...19999].

Also cleaned up the code somewhat.

Also changed the loop in close_conn() to go over the dict's values,
since those are all that's used.

following item:

Picklers are not re-entrant!  The only place where the shared global
pickler was used was in the error handling in store(), to test whether
the caught exception can be pickled (else it would fail when sending
the response).  Change the flow control to create a new pickler
locally, only when an exception is caught.  (When no exception is
caught, we know newserial is a string so there's no need to test its
picklability.)

in the docstring that filter should be None.  Also change the return
value if filter!=None from () to [], to match the type of what it
returns in other cases.

methods here.

the server to take the "async=0" path which could cause recursive
calls to message_input() or message_output(), which would hang due to
the input/output locks.