Received: (qmail 12492 invoked by uid 2012); 3 Aug 1998 11:12:51 -0000
Message-Id: <19980803111251.12491.qmail@hyperreal.org>
Date: 3 Aug 1998 11:12:51 -0000
From: Hans Werner Strube <strube@physik3.gwdg.de>
Reply-To: strube@physik3.gwdg.de
To: apbugs@hyperreal.org
Subject: Rotation of logs and suppression of logging is not well solved.
X-Send-Pr-Version: 3.2

>Number:         2767
>Category:       mod_log-any
>Synopsis:       Rotation of logs and suppression of logging is not well solved.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Mon Aug  3 04:20:00 PDT 1998
>Last-Modified:  Mon Aug  3 10:44:10 PDT 1998
>Originator:     strube@physik3.gwdg.de
>Organization:
>Release:        1.3.1
>Environment:
Any (here: Solaris 2.5+)
>Description:
It is a pity that the rotation of log files is not handled by the server's log
module itself but has to be done by the additional rotatelogs program.
This program should also be enhanced (I have done this myself) by taking into
account the local timezone and DST and using a readable time as file extension
instead of the internal Unix time, for instance, file.YYMMDDhh (no resolution
below an hour will be required; thus I changed the rotation-period argument
into days[.hours]). But all this should be built into the log module itself.
Further it should be possible to specify host-address patterns whose access
should not be logged (e.g., the local domain or local search robots).
Even the old CERN httpd allows this. I also built this into rotatelogs in a
very crude way, but this is clumsy.
>How-To-Repeat:
N.A.
>Fix:
Own hacks to rotatelogs.c, but would prefer change of mod_log_config
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Mon Aug  3 10:44:09 PDT 1998
State-Changed-Why:
This has been discussed many times, and the conclusion was
that there is no point in adding hard-coded, fixed utility
code to the logging module when people can do whatever they
want with piped logs.  If you try to support what everyone
wants in the logging module itself, it becomes so bloated
it is crazy.
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]