Dmitry Semyonov
2009-Feb-23 09:50 UTC
[Logcheck-devel] Bug#463793: rsyslogd restarts are not ignored
On Mon, 4 Feb 2008 08:15:24 +1300, martin f krafft wrote:> logcheck has the policy not to ignore restart messages. Thanks for > the patch, please understand that I won't be including it.Quote from README.logcheck-database: "Unfortunately, we don't have the time to add and update rules for everything, therefore the following exceptions apply: * Debug messages * Messages produced by software not included in Debian * Temporary messages which are due to a bug in the package * Messages related to daemon startups and shutdowns Please do not file bugs related to these messages." As I understand, the rationale for not fixing the bug is "we don't have the time to add and update rules for everything". But since Lenny release, rsyslog no longer falls into the "everything" category. It is now the default system logger, recommended to be used on every Debian machine which does not have any specific syslog requirements not met by rsyslog. So, you can imagine how much time will be wasted by Debian users on the whole to manually disable these daily notifications just because you don't want to make an exception for "the policy". (On the other hand, I understand that it's too late already.) P.S. One of the main reasons why I chose logcheck in favor of logwatch is that the former sends notifications for 24/7 PCs only when needed instead of every day. This, in my opinion, should be the ultimate logcheck policy for default Debian installs. -- ...Bye..Dmitry.
martin f krafft
2009-Feb-24 19:32 UTC
[Logcheck-devel] Bug#463793: rsyslogd restarts are not ignored
also sprach Dmitry Semyonov <linulin at gmail.com> [2009.02.23.1050 +0100]:> As I understand, the rationale for not fixing the bug is "we don't > have the time to add and update rules for everything". But since Lenny > release, rsyslog no longer falls into the "everything" category. It is > now the default system logger, recommended to be used on every Debian > machine which does not have any specific syslog requirements not met > by rsyslog. So, you can imagine how much time will be wasted by Debian > users on the whole to manually disable these daily notifications just > because you don't want to make an exception for "the policy". (On the > other hand, I understand that it's too late already.)Why does rsyslog generate a log message every day? Also, it's true, we have very little time. If you are interested in improving logcheck, would you join the team? I'd be happy to give you commit access and let you hack away a bit. Maybe it would be best if you cloned Git first and sent in a few patches so that I have a good reason to give you write access. Oh, and you also need an account on alioth.debian.org. Thanks, -- .''`. martin f. krafft <madduck at d.o> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) Url : http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20090224/cab75c61/attachment.pgp
Possibly Parallel Threads
- Bug#463793: rsyslogd restarts are not ignored
- Bug#500017: ignore.d.server/ssh: outdated 'reverse mapping checking ... failed' rule
- Bug#561995: mkdir: cannot create directory `/var/lock/logcheck': Permission denied
- helping out on logcheck
- Bug#554828: logcheck: Please include rules for amd (automount daemon from am-utils package)