logwatch does not report cron events
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
logwatch (Debian) |
Fix Released
|
Unknown
|
|||
logwatch (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: logwatch
Hello,
Debian/Ubuntu ships a cron service definition (in dist.conf/
Currently, it looks like this:
*OnlyService = (CROND|
However, the logfile entries for cron look like this, so they don't match:
Feb 16 09:11:11 deimos cron[641]: (CRON) INFO (pidfile fd = 3)
Feb 16 09:11:11 deimos cron[654]: (CRON) STARTUP (fork ok)
Feb 16 09:11:11 deimos cron[654]: (CRON) INFO (Running @reboot jobs)
Feb 16 09:17:01 deimos CRON[923]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
I suggest changing the OnlyService statement to this (patch attached):
*OnlyService = (CRON|cron|
This applies to all Ubuntu releases, from at least Lucid to Natty.
Thanks!
Related branches
- Martin Pitt: Approve
-
Diff: 437 lines (+174/-30)5 files modifieddebian/changelog (+17/-0)
debian/dist.conf/services/cron.conf (+1/-1)
logwatch.8 (+2/-3)
scripts/logwatch.pl (+12/-4)
scripts/services/named (+142/-22)
CVE References
Changed in logwatch (Debian): | |
status: | Unknown → New |
Changed in logwatch (Debian): | |
status: | New → Fix Committed |
Changed in logwatch (Debian): | |
status: | Fix Committed → Fix Released |
Oliver, thanks for taking the time to file this bug report and help us make Ubuntu better!
This is indeed a problem on natty, and I've confirmed it on Debian unstable as well.
I forwarded the issue and the patch upstream to Debian, and I'm marking this bug as Triaged, setting Importance to Medium.