Nikolaus Rath
2007-Apr-07 10:24 UTC
[Logcheck-devel] Bug#418147: logcheck: Does not complain if rules are unreadable
Package: logcheck Version: 1.2.39 Severity: normal Hello, Due to the incorrect group ownership bug (which has already been fixed) I ended up with logcheck not being able to read any files in /etc/logcheck/ignore.d.paranoid. However, instead of complaining that some files were unreadable, logcheck just sent the *complete* logfiles by mail, without any filtering. If logcheck cannot read some of its rule files, it should mention that in its mail. Additionally, it may be worth considering to not include any logfile contents in this case, since for me this generated a 10 MB mail. Best, Nikolaus -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.9-023stab039.1-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages logcheck depends on: ii adduser 3.63 Add and remove users and groups ii cron 3.0pl1-86 management of regular background p ii debconf [debconf 1.4.30.13 Debian configuration management sy ii debianutils 2.8.4 Miscellaneous utilities specific t ii exim4 4.50-8sarge2 metapackage to ease exim MTA (v4) ii exim4-daemon-hea 4.50-8sarge2 exim MTA (v4) daemon with extended ii lockfile-progs 0.1.10 Programs for locking and unlocking ii logcheck-databas 1.2.39 A database of system log rules for ii logtail 1.2.39 Print log file lines that have not ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent ii sysklogd [system 1.4.1-17 System Logging Daemon -- debconf information excluded
Debian Bug Tracking System
2017-Jan-25 22:09 UTC
[Logcheck-devel] Bug#418147: marked as done (logcheck: Does not complain if rules are unreadable)
Your message dated Wed, 25 Jan 2017 22:05:36 +0000 with message-id <E1cWVhA-0002vU-Nx at fasolo.debian.org> and subject line Bug#418147: fixed in logcheck 1.3.18 has caused the Debian Bug report #418147, regarding logcheck: Does not complain if rules are unreadable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 418147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418147 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Nikolaus Rath <Nikolaus at rath.org> Subject: logcheck: Does not complain if rules are unreadable Date: Sat, 07 Apr 2007 12:24:30 +0200 Size: 2818 URL: <http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20170125/64a649e8/attachment-0002.mht> -------------- next part -------------- An embedded message was scrubbed... From: Hannes von Haugwitz <hannes at vonhaugwitz.com> Subject: Bug#418147: fixed in logcheck 1.3.18 Date: Wed, 25 Jan 2017 22:05:36 +0000 Size: 7742 URL: <http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20170125/64a649e8/attachment-0003.mht>