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
I think the idea was that startup/shutdown is an unusual event, which
typically occurs after a human intervention. If Apache goes down by
itself, I sure as hell want to know about it. If it's restarted because
of an upgrade, I don't mind the email; that's just part of the upgrade
process.
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.)
--
MSDOS didn't get as bad as it is overnight -- it took over ten years
of careful development.
-- dmegg...@aix1.uottawa.ca
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
