On Wed, Sep 16, 2009 at 5:28 AM, Christian Zagrodnick <c...@gocept.com> wrote:
> The zc.zope3recipes:instance recipe creates a zdaemon.conf which writes
> the transcript_log and zdaemon's eventlog to the same file. That's
> actually fine.
>
> ZDaemon's reopen_transcript does exactly that: it reopens *only* the
> transcript. So when rotating the logfile (as zc.zope3recipes does it
> via logrotate) ZDaemon messages still go to the old logfile.
>
> I see two obvious ways to fix that:
>
> a) Write ZDaemon's eventlog to stdout

That won't help.  The messages are coming from the controller.

> b) Add a sane way to reopen the logfile.  There is a logreopen command
> in ZDaemon but that actually restarts the daemon process.
>
> Comments? Suggestsions?

The controller needs to be more careful about how it manages it's log
file.  It needs to keep track of the handler used and, when the
transacript file is reopened, it needs to remove the old handler it
was using and create a new one.
This is probably complicated by ZConfig which is managing the logging
configuration.  This is easy to deal with if you're willing to rely on
the logging systems internal details. :)

Jim

-- 
Jim Fulton
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to