[Logwatch-Devel] .gz in the logfile conf files CVS commit
lude at informatik.uni-tuebingen.de
Wed Sep 28 14:31:01 MST 2005
On Mon, Sep 26, 2005 at 10:11:17AM -0700, Mike Tremaine wrote:
> On Wed, 2005-09-14 at 00:18, David Baldwin wrote:
> > >>The question here is should we restore .gz to all conf/logfile/*.conf
> > >>files or should this be left for the end user?
> > >>
> > > Well, logrotate creates files like "foo.number.gz", so I guess at least
> > > that is a pretty common setting. With "delaycompress" or without
> > > compression, it is only foo.##, so for the above example secure.*.gz
> > > and secure.* seem to be common settings that would handle plenty of
> > > situations.
> > .N (uncompressed)
> > -YYYYMMDD (uncompressed)
> > .N.gz (compressed)
> > -YYYYMMDD.gz (date extension, compressed)
> > Hence would need 'archive' options:
> > archive secure.*
> > archive secure-*
> > archive secure.*.gz
> > archive secure-*.gz
> Ok so I went through the conf/logfiles/
> And added .gz to these files
> Those not listed seemed to require enough user intervention to use, in
> general, or not have Archive listed so they got skipped.
> Also rather then add the "-" in each case [especially in cases like
> httpd.conf] I added a note about it instead.
in conf/logfiles/sonicwall.conf there seems to be a typo:
Archive = archiv/sonicwall.log.*,gz
maybe should read:
Archive = archiv/sonicwall.log.*.gz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www2.list.logwatch.org/pipermail/logwatch-devel/attachments/20050928/e06ed192/attachment.bin
More information about the Logwatch-Devel