From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311
Description of problem:
logwatch as shipped with Enigma errata and Skipjack-beta2 fails to parse
/var/log/cron and /var/log/samba/log.* due to date preprocessing code which is
out-of-date and incompatible with the current format of dates in /var/log.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. su -l root
2. logwatch --debug=10 --detail=10 &> out.txt
3. less out.txt and look at logwatch mail to root
Actual Results: The log file preprocessors for cron and samba don't match any
line at all.
Notice how /etc/log.d/scripts/logfiles/cron/applydate is called and checks for a
wrong date prefix. That filter ought to be dropped. Cron logs in standard date
Also notice how Samba's logs seem to be checked for a wrong date format, too,
(at least debug output says that) but internally the Perl script checks a second
format. Unfortunately, it gets that one completely wrong, too, and doesn't strip
off the carriage return, and additionally uses a wrong regular expression that
is incompatible with the Samba log format of Red Hat Linux.
I'll attach one possible fix, but my motivation to fix logwatch is close to
Created attachment 53504 [details]
patch against logwatch-2.6-1
applied in 2.6-2, thanks