Ah sorry, I think I know what this is. Let me look again.
** Changed in: logcheck (Ubuntu)
Status: Incomplete => New
** Changed in: logcheck (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
** Tags added: server-todo
--
You received this bug notification because you are a
Hi Robie, Thank you for digging into this. There is a difference in the
log entries posted by the cron service. On my system, it does post
Apr 05 14:57:01 logcheck CRON[6191]: pam_unix(cron:session): session
opened for user root(uid=0) by root(uid=0)
while on your system, it does post
Apr 05
Thank you for reporting this bug and helping to make Ubuntu better.
As far as I can tell, the line you've provided should be matched by the
following line, from /etc/logcheck/ignore.d.paranoid/cron:
^(\w{3} [ :0-9]{11}|[0-9T:.+-]{32}) [._[:alnum:]-]+ CRON\[[0-9]+\]:
** Changed in: logcheck (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059857
Title:
logcheck report flooded with cron session lines
To
** Changed in: logcheck (Ubuntu)
Status: New => Triaged
** Changed in: logcheck (Ubuntu)
Importance: Undecided => Medium
** Tags added: server-todo
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
