zope33_devel branch at this time.

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.

It looks like Connection refused errors in the test suite are the
result of a server taking a long time to get started -- usually when
the BDBStorage takes a long time to create.

transaction, not the position of the first record.

Not sure why this happens.

If you grep for just the Trans lines, it's probably more useful to
have the size than the offset.  Maybe.

and remove old comment about disconnected errors.

These are no longer used in Zope.

- remove commented-out cruftiness related to a no-longer-supported
  model

that the first thread to launch managed to commit each time, while the
other 3 threads got nothing but conflict errors.  Added some randomization
to boost the odds of success, and to prevent systematic favoring of any
thread.  That appears to work.

Synchronous is what matters for the tests.

Move two class variable definitions into __init__(), because class
variables defined in __slots__ are immutable.  This should still be a
net memory savings, because the a 8-entry dict and a 10-entry dict
both have the same allocated size.

tricks left name thread undefined at runtime.  Repair that.  Plus
add comments, use meaningful variable names, stop pretending we can run
on a system without threads, and don't use "id" (a builtin name) as a
local vrbl name.

caught by pychecker