Fwd: suggestion to handle stock Fedora 8 logrotate changed extension on archived log files

---------- Forwarded message ----------
From: Damon Hart <[email protected]>
Date: Mon, Feb 11, 2008 at 5:44 AM
Subject: suggestion to handle stock Fedora 8 logrotate changed
extension on archived log files
To: [email protected]


Following up on some items I found missing in my logwatch daily recap
 email, I see that events occurring prior to log rotation were not
 reflected in logwatch. Comparing different machines, it looks like this
 problem occurs (in my case) only on Fedora 8 (vs earlier Fedora
 revisions.) Further poking around suggests that the problem arises
 because of the stock Fedora 8 logrotate convention for naming archived
 log files. These filenames are now:

 messages.20080210
 messages.20080203
 messages.20080127
 messages.20080120

 instead of the prior convention:

 messages.1
 messages.2
 messages.3
 messages.4

 and similarly for other log files. The slight wrinkle in handling this
 from a logwatch programmers point of view is that a filename sort
 (alphabetical) will result in a oldest to newest ordering instead of
 newest to oldest.





-- 
Kirk Bauer <[email protected]>
http://linux.kaybee.org | www.logwatch.org
Author, Automating UNIX & Linux Administration