Bug#1076745: logcheck-database: cron rules

2025-04-27 Thread Mathias Gibbens
control: tags -1 + pending signature.asc Description: This is a digitally signed message part

Bug#1076745: logcheck-database: cron rules

2024-11-10 Thread R Lewis
> ^(\w{3} [ :0-9]{11}|[0-9T:.+-]{32}) [._[:alnum:]-]+ CRON\[[0-9]+\]: > pam_[[:alnum:]]+\(cron:session\): session (opened|closed) for user > [[:alnum:]-]+(\(uid=[[:digit:]]+\))?( by \(uid=[0-9]+\))?$ > > Notice the "by" now has a username > > The fix is pretty easy, add an optional second usernam

Bug#1076745: logcheck-database: cron rules

2024-07-22 Thread Craig Small
Package: logcheck-database Version: 1.4.3 Severity: normal Hi, I'm getting logcheck entries like: Jul 23 06:02:01 myhost CRON[566969]: pam_unix(cron:session): session opened for user logcheck(uid=124) by logcheck(uid=0) The relevant mis-matching line is in paranoid.d/cron: ^(\w{3} [ :0-9]{1