regression: logcheck doesn't suppress irrelevant messages

Bug #503714 reported by Ralf Hildebrandt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
logcheck (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: logcheck

After an upgrade from jaunty to karmic, logcheck reports a LOT of cron messages:

Jan 5 22:39:01 de CRON[3267]: (nobody) CMD (if [ -x /usr/bin/php5 ] && [ -f /usr/share/serverstats/update.php ]; then /usr/bin/php5 /usr/share/serverstats/update.php > /dev/null; fi)

Jan 5 22:39:01 de CRON[3270]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin

Jan 5 22:40:01 de CRON[3324]: (root) CMD (test -x /usr/sbin/mcelog -a ! -e /etc/mcelog-disabled && /usr/sbin/mcelog --ignorenodev --filter >> /var/log/mcelog)

It seems that ALL cron messages come through.

ProblemType: Bug
Architecture: amd64
Date: Wed Jan 6 09:52:11 2010
Dependencies:

DistroRelease: Ubuntu 9.10
Package: logcheck-database 1.2.69
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-server
SourcePackage: logcheck
Uname: Linux 2.6.31-16-server x86_64

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.