On Mon, Feb 09, 2004 at 01:52:37AM +1100, Gautam Gopalakrishnan wrote: > On Sun, 8 Feb 2004 06:13:13 -0800 > "Loren M. Lang" <[EMAIL PROTECTED]> wrote: > > > Is there a good program that can monitor a daemon and take an > > appropriate action if the daemon dies? I am having trouble with > > ClamAV dying in certain circumstances, but somewhat rare. I would > > like for when it dies, to either restart it or copy a mail config file > > for exim over the default and signal Exim which would then disable > > exim from using clamav so the mail will still come through. Currently > > we have it disabled until the problem is fixed, but some users are > > still not heeding the warnings and are infecting themselves with the > > MyDoom virus which ClamAV was previously blocking. > > /usr/ports/sysutils/daemontools > http://cr.yp.to/daemontools.html
I took a look at this as well as monitord in the ports collection, but neither seems to do exactly what I'm looking for. I want a way to take an action other than restarting the service if the service dies, because I think that ClamAV will keep dying as long as exim is sending it the same email that caused it to crash in the first place, instead I just want to disable exim from using clamav in it's config file until someone can manually intervene and fix the problem. > > hope that helps. > Gautam -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
pgp00000.pgp
Description: PGP signature