Bug#251404: [Logcheck-devel] Bug#251404: logcheck-database: rules don't match non local syslog messages

maks attems debian at sternwelten.at
Thu Jun 3 11:37:19 UTC 2004


On Thu, 03 Jun 2004, Christoph Martin wrote:

> > well logcheck removes trailing slashes whitespace before log
> > entry is processed.  so your bug report seems wired to me.
> 
> It might be that this was fixed some time ago with the removing of
> trailing whitespace. I try to check it at the moment. But it takes some
> time since I had some problems with the introduction of the logcheck
> user . My /var/lib/logcheck/offset* files were owned by root, so
> logcheck was checking all time from the beginning, which resulted in
> very large and also late mails.

changelog indicates that the fix is done since 1.2.17:
  * Strip leading and trailing whitespace from log entries before
    processing them.  (Closes: #238513)

so yes it would be interesting if this cron messages are still
reported with newer version, than the sed processing needs 
to be fixed inside of logcheck.

regarding the logcheck user everything should be fixed since 1.2.20a
(the current sarge version, sid has 21 in it's upload queue)
 
> > are you using logcheck-database outside of logcheck,
> > or did logcheck report aboves line?
> 
> I only use it inside logcheck.

ok thanks for the further clarification,
would be nice to have that nailed down.

a++ maks






More information about the Logcheck-devel mailing list