the logging system for zeo instances is inconsistent

[Fabio Tranchitella]

Hi,
I'm the Debian and Ubuntu maintainer of Zope 3. We are trying to have ZEO
running in a FHS compliant way and as non-root user, but there are some
issues related to the logging subsystem.

First of all, if I modify the zeo.conf and specify a non-root user (let's say zope), and
then I start the instance from zeoctl using the root user, the log file is created by
the root (owner root:root, permissions 644) and the forked zeo server refuses to
start because it can't write to the log file. Fair.

Second problem: it seems that zeoctl has support for sending a logreopen
command to the zeo instance (./bin/zeoctl logreopen) but there is no handling
code for the SIGUSR2 signal in the zeo runner. This means that I can't use logrotate
to, well, rotate the logs of a zeo instance.

Thanks in advance,
Fabio

[Jim Fulton (jim-zope)]

On the first point, could you provide a sample configuration file (or files) that illustrate the problem?

[Jim Fulton (jim-zope)]

The second part of this report, reopening log files in SIGUSR2 will be fixed (3.10b7).
See https://bugs.launchpad.net/zodb/+bug/143600