Hi ! > 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.
Montioring sensitive service is a normal process in a production environement IMHO. > 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. As several administrators I know a general tool like monit can do this job very well and even restart clamd when it is blocked with a biiig mail sometimes. There is even examples on monit website to show how to do that. /Xavier _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
