httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Hess" <>
Subject Re: reworking of cronolog as mod_cronolog (or folding into mod_l
Date Mon, 20 Dec 1999 17:28:12 GMT
As I understand cronolog, it tries to log lines perfectly to logs for the
appropriate time periods (based on the beginning of the request, or the
end?  Makes little difference, I suppose).  So sending a SIGUSR1 might
result in a few lines sneaking from the previous day's logs to the next.

If a cronolog module wants to be able to "perfectly" split across logs
based on time, the parent could open two logfiles (one for the current
period, one for the next period), then the children could internally switch
to the next logfile at the appropriate time.  After the next period begins,
a SIGUSR1 to the parent should work to progress forward to the next


----- Original Message -----
From: Martin Kraemer <Martin.Kraemer@Mch.SNI.De>
To: <>
Sent: Monday, December 20, 1999 8:19 AM
Subject: Re: reworking of cronolog as mod_cronolog (or folding into mod_l

> On Sun, Dec 19, 1999 at 08:43:31PM +0100, Martin Kraemer wrote:
> > I can only decide about it when I know how the ownership will be
> > +1 if nothing changes against the current situation (except for the
> > functionality).
> I imagine that the reopening of the logfiles could be limited to the
> point(s) in time where the server is restarted. Simply sending a SIGUSR1
> at midnight would automatically rotate "per day" (combined with the
> modifications of mod_log_config, and an appropriate configuration) or
> per month or whatever.
>     Martin
> --
>   <Martin.Kraemer@MchP.Siemens.De>      |       Fujitsu Siemens
>        <>              |   81730  Munich,  Germany

View raw message