GitLab

Re-add the zeoctl module to ZEO, and rewrite runzeo so
it can run as a main program (the scripts created by
mkzeoinstance.py expect to be able to do this).

- References to headers now involve the package names.

- The zpkg support files have been moved to the top-level directory,
  and the releases/ tree has been removed.  The resource map and
  configuration file have been combined now that zpkg allows that.

- The scripts are now all located in src/scripts/ in a checkout.

- Scripts that were imported in the tests have been split into library
  and script components; the library portions share name of the
  script (in order to reduce changes).  The library portions may not
  be used as scripts directly.

Use ZConfig's new socket address types appropriately.

These config file keys changed:

section    key              was             is
-------    ---------------  --------------  -------------------------
zeo        address          socket-address  socket-binding-address
zeo        monitor-address  socket-address  socket-binding-address
zeoclient  server           socket-address  socket-connection-address

Collector 1788:  runzeo fails in 2.8

A patch from Mark Hammond to repair a new Windows-specific
gimmick in ZEOServer.setup_win32_signals().

There is no logging level named EXCEPTION.

Port ZEO changes for Windows from ZODB 3.2.

In addition, repaired the useless default logging in runzeo.py.

Here's Sidnei's Zope 2.7 checkin comment:

* Borrow Zope's 'Signal' mechanism for Windows, if available, to
  implement clean shutdown and log rotation handlers for Windows.

* Back to creating a .PID for ZEO, so external programs that wish to set
  the 'signal' can get the PID and therefore derive the signal name.
  Currently only necessary on Windows but created on all platforms which
  implement os.getpid(), as long as the 'pid-filename' option is set,
  or the 'INSTANCE_HOME' environment variable can be found.

to zLOG other than a few comments.

This definitely broke the log analyzers pretty bad.

logging directly

Bug fix from Jon Dyte.

configuration file can be used for both the runzeo and zeoctl scripts.
This makes it easier to keep all the configuration needed to support the
ZEO server process in a single file.
For more explanation of the changes, see
http://zope.org/Members/fdrake/WikiBlog/ZEOServerConfiguration

The file used to be called runsvr, but was changed.  Change the label
to RUNZEO to match the name of the file.

Add the process ID to distinguish different processes when tests are
running.

  - Make ZEO server actually startable.  Note that the ZConfig option
    for the authentication database is named 'database', while the
    equivalent argument to the StorageServer initializer is called
    'filename':  "One of these things just doesn't belong!"

After the merge, I made several Python 2.1 compatibility changes for
the auth code.

default.

types.

that we can get distutils install to munge the #! line to insert the
proper Python executable file name.  (/usr/local/bin/python would work
too, but may not be the Python version that you intended to use, so
IMO it's better to require that you use an explicit Python interpreter
when invoking the scripts before they are installed.

runzeo.py lives -- that didn't work when runzeo.py is installed in
/usr/local/bin.

Handing off to Barry.

Also, remove unused reuse_addr arg to ZEO.zrpc.server.  The server was
always calling set_reuse_addr().

No tests yet, that's the next step.  Simple functional tests work.

- Now that ZEO/schema.xml is installed, use ZEO.__file__ to find it.

schema.