If syslog-summary isn't interested in fixing this "bug", adding this egrep
would fix it on logcheck's side. Though the egrep isn't perfectly
paranoid - maybe you would want a ^[0-9]+ at the beginning?
It seems to me that syslog-summary should fix it on their side:
< if not QUIET or order:
< print "%8d Patterns to ignore" % len(ignore_pats)
< print "%8d Ignored lines" % ignored_count
--
if not QUIET or order:
if len(ignore_pats):
print "%8d Patterns to ignore" % len(ignore_pats)
if ignored_count:
print "%8d Ignored lines" % ignored_count
And then all logcheck would need to do is call syslog-summary with --quiet
(to get rid of the 0 lines skipped message)
Fix on logcheck's side:
246,247c246,247
< $SYSLOG_SUMMARY "$TMPDIR/checked" | \
< egrep -v "^Summarizing " | cat >> "$TMPDIR/report" \
---
$SYSLOG_SUMMARY -q "$TMPDIR/checked" | \
egrep -v "( Patterns to ignore| Ignored lines|^Summarizing )" | cat >>
"$TMPDIR/report" \
