-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
Jens Vagelpohl wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien Anguenot wrote:
Jens Vagelpohl wrote:
On 30 Jun 2006, at 13:40, Julien Anguenot wrote:
Yesterday night, we were having a long nightly running process (several
hours) on one of the ZEO node. (Around 500 Mo logs on this one). The
reopen
On 6/30/06, Tres Seaver [EMAIL PROTECTED] wrote:
I think the shift to the oh-so-much-better Python logging module is not
complete. See this bit in ZEO/runzeo.py:
Aha. Indeed, we are running ZEO, and my failed attempts of reproducing
this did not use ZEO. :)
--
Lennart Regebro, Nuxeo
I've been developping some packages using zope.testing and the
testrunner that ships with zope2.10. Yesterday, I packaged these using
fairly standard python/egg pattern. one package is pure python, the
other a zope2/zope3 hybrid.
now I have two large PITAs:
1. in general, this would suck
