On Wednesday 27 October 2004 08:00 pm, mike.sanchez wrote: > On Wed, 27 Oct 2004, Joe Maimon wrote: > > > The ClamAV authors could put a stop to this by making clamdscan and > > > clamscan the same program and then acting differently depending on > > > which name is run. This is similiar to how gzip and gunzip are > > > >An action could then be taken to > >alert someone if clamd died (|sendmail [EMAIL PROTECTED]). When clamd > >hangs on our system, mail is deferred until I realize mail has stopped and > > as you can imagine, that is a bad thing. > > I run a cron once an hour that runs freshclam and does some clamd checks. > If clamd is not running or errors, an email is sent, any clamd processes > are killed and a new clamd is started.
as you can imagine, that's orders of magnitude more complicated than running the two under daemontools or runit (both do essentially the same thing) http://cr.yp.to/daemontools.html http://smarden.org/runit/ -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail GnuPG Key ID: 481BF7E2 ++ scriptkitchen.com/kitchen.asc
pgpFbarbxWlkX.pgp
Description: PGP signature
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
