Binary package hint: logcheck-database
Ubuntu 9.10, upgraded from 9.04. logcheck-database 1.2.69 from karmic/main
logcheck is supposed to suppress cron lines that just log "CMD", according to /etc/logcheck/ignore.d.paranoid/cron which contains:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ /USR/SBIN/CRON\[[0-9]+\]: \([_[:alnum:]-]+\) CMD \(.*\)$
This used to work on 9.04, however, on 9.10 CRON no longer logs its full path name, example from /var/log/syslog:
Oct 29 17:50:01 host1 CRON[8504]: (user1) CMD (/usr/local/bin/getmail -r /home/user1/.getmail/getmailrc)
Which makes these lines appear in the logs. Annoying for jobs on a 5-minute basis...
Suggested fix: adjust the filter line from /etc/logcheck/ignore.d.paranoid/cron shown above and remove the /USR/SBIN part.
Binary package hint: logcheck-database
Ubuntu 9.10, upgraded from 9.04.
logcheck-database 1.2.69 from karmic/main
logcheck is supposed to suppress cron lines that just log "CMD", according to /etc/logcheck/ ignore. d.paranoid/ cron which contains:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ /USR/SBIN/ CRON\[[ 0-9]+\] : \([_[:alnum:]-]+\) CMD \(.*\)$
This used to work on 9.04, however, on 9.10 CRON no longer logs its full path name, example from /var/log/syslog:
Oct 29 17:50:01 host1 CRON[8504]: (user1) CMD (/usr/local/ bin/getmail -r /home/user1/ .getmail/ getmailrc)
Which makes these lines appear in the logs. Annoying for jobs on a 5-minute basis...
Suggested fix: adjust the filter line from /etc/logcheck/ ignore. d.paranoid/ cron shown above and remove the /USR/SBIN part.