This bug was fixed in the package logcheck - 1.4.3ubuntu1
---
logcheck (1.4.3ubuntu1) plucky; urgency=medium
* d/p/fix-cron-by-rules.patch: Ignore cron session opened msgs.
(LP: #2059857)
-- Bryce Harrington Wed, 04 Dec 2024 17:56:43
-0800
** Changed in: logcheck (Ubuntu)
** Changed in: logcheck (Ubuntu)
Status: In Progress => Fix Committed
--
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 manage n
** Tags added: patch
--
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 manage notifications about this bug go to:
https://bugs.launchpa
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/logcheck/+git/logcheck/+merge/477783
--
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 flood
I found a Debian bug about this issue with some discussion, and used
that to make the attached patch. I've requested feedback from Debian
about it.
** Patch added: "fix-cron-by-rules.patch"
https://bugs.launchpad.net/debian/+source/logcheck/+bug/2059857/+attachment/5842228/+files/fix-cron-by-
** Changed in: logcheck (Debian)
Status: Unknown => New
--
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 manage notifications a
** Bug watch added: Debian Bug tracker #1076745
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076745
** Also affects: logcheck (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076745
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
** Changed in: logcheck (Ubuntu)
Assignee: Robie Basak (racb) => Bryce Harrington (bryce)
--
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
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 memb
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 14:
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]+\]:
pam_[[:alnum:]]+\(cron:session
** 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 ma
** 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.
ht
13 matches
Mail list logo
