>Number: 5492 >Category: other >Synopsis: feature request for logrotate+logresolve >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Sun Dec 19 05:20:01 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.9 >Environment: Linux margo.student.utwente.nl 2.2.12 #4 Mon Nov 15 16:46:32 CET 1999 i586 unknown >Description: The current logrotate and logresolve have (in my eyes) confusing interfaces. I think this is part of the reason neither are installed in linux-distributions. (Especially the "when" of logrotate is not human-friendly) >How-To-Repeat:
>Fix: I think logrotate should accept a similar "when" configuration as the crontab. In addition, if logresolve could be integrated into logrotate, it would be possible to start up a separate process which will resolve the names in the freshly created old logfile. To finish things off, the logfile could then be compressed using the compression-tool of your choice. configuration should be via httpd.conf: LogrotateResolve Yes/No LogrotateCompress /usr/bin/bzip2 /usr/bin/gzip ErrorLog "|/usr/local/apache/bin/rotatelogs /var/log/apache/error_log 00 00 * * mon" >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]
