-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30 Jun 2006, at 14:30, Julien Anguenot wrote:
For maximum reliability I tend to forego the built-in log reopening in favor of using the logrotate utility in "copytruncate" mode. This will not require any log file reopening, logrotate will simply make a copy of the existing log and then truncate the logfile that continues to be in use to zero length. Zope or the ZEO server won't have to know or care at
all at that point.

Thank you Jens for the quick reply.

I think I'm going to send these instructions, to be on the safe side, to
the administrators taking care of the cluster.

Do you have any idea about the "zopectl logreopen" misbehavior as
someone who's avoiding using it explicitly ;) ?

I'm afraid I don't. I have seen issues myself where the server would just die and not come up again, but never investigated it. The logreopen solution offers a safe and lasting fix and it even simplifies log rotation configuration.

Here's a very simple one that rotates ZEO server and client logs for a simple one-client ZEO setup, we use it for www.zope.de:

[EMAIL PROTECTED] ~]$ cat /etc/logrotate.d/zope.de
/home/zope/zope.de/log/*.log {
        weekly
        rotate 10
        missingok
        compress
        copytruncate
}


jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEpRxuRAx5nvEhZLIRAu2QAKCMo1tttOQGULCRcWlYcVRn4psWrwCfXoAk
1ycxYnJQNbCz/Ab+KYJUh+A=
=rYwK
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to