On Mon, 2009-08-24 at 11:28 -0400, Frédéric Brière wrote: > On Wed, Aug 19, 2009 at 08:08:18PM +0200, martin f krafft wrote: > > When I joined logcheck, there was an unwritten policy not to filter > > startup and shutdown messages. I don't know if that extends to ... > But yeah, if rsyslog emits these messages as a matter of course, they > should be filtered IMO. Missing a potential theoretical shutdown of > rsyslog is a lesser evil, compared to annoying the sysadmin with > messages that will be ignored anyway. > > (One possible idea would be to peg the restart rule to the approximate > time of day when cron.daily is run.
One other option would be to create some rsyslog configuration statements that can be used to suppress these kind of messages. This is not very hard, almost trivial. There would one switch be required for the startup/shutdown message and probably another one for the message that is emitted when rsyslogd is HUPed. Would that be useful? If so, I'd consider to implement it relatively soon (but only in the current v5 devel version). Rainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
