Package: logwatch
Version: 7.1-2
Severity: normal
X-Debbugs-CC: richardaburton at hotmail.com
Filing as a new bug, to have it publicly tracked. I hope the X-Debbug-CC
works and you get the bug Id to answer to.
> I was just wondering if you'd seen this bug (346502), it's filed
against
> logcheck-database (whatever that is), but it looks it's just another
> logwatch unmatched entry. I'm also seeing it in my logwatch output, but
> I didn't want to raise another bug with you while this one was open.
> Maybe it was just opened against the wrong package? Either way I figured
> you probably hadn't seen it since you fixed the syslogd one so quickly,
> and I imagine this would be just as quick.
logcheck-database is a completly different package. I should probably
subscribe there in the PTS, but that should not stop you from filing
bugs on logwatch. I much easier to track for me.
Can you please see in you logs if these messages are all accompanied by a
su (pam_unix)
message, that ends up in logwatch? In that case, and from reading the
#190215, which is the cause, I expect that I can just ignore this line,
otherwise I need to take care and output a summary.
Willi
