[Logcheck-devel] Bug#542663: logcheck: /etc/cron.d/logcheck runs?too often (now every 2 hours)
martin f krafft
madduck at debian.org
Fri Aug 21 18:53:34 UTC 2009
also sprach Frédéric Brière <fbriere at fbriere.net> [2009.08.21.2027 +0200]:
> > I think this is suboptimal. I'd like the next generation of
> > logcheck to be a daemon scaping the syslog socket and be able to
> > react immediately.
>
> I sure hope this will involve some throttling of some sort. When
> things go wrong, the last thing you want is an email flood.
Yes, it should be exponential backoff based on counters on
individual rules matched.
--
.''`. 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
"they that can give up essential liberty
to obtain a little temporary safety
deserve neither liberty nor safety."
-- benjamin franklin
-------------- 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/20090821/81c8828d/attachment.pgp>
More information about the Logcheck-devel
mailing list