Hi! In my case just restarting clamd wouldn't have worked, because clam didn't start because of a broken database (or a least one file in the database directory which doesn't belong there). And because of that clamscan as backup didn't worked either.
Tom > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Lyle Giese > Sent: Wednesday, April 11, 2007 4:17 PM > To: clamav-users@lists.clamav.net > Subject: [Clamav-users] Clamdmon.sh > > > I am amazed at the number of people here that apparently not using > SOMETHING to monitor clamd. Esp. when the developers include a nice > script to check and restart clamd. > > I run three different mail servers and quickly found clamdmon > and just a > bit of PERL programming created a means of being notified of > an issue. > Yes, you have to have a means of being notified 'out of band'. But if > you are serious about uptime, you need to know promptly when a mail > server is not processing email and at that point you cann't depend on > that email server to tell you it's broken. > > Lyle > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit > http://wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
