On 2011-02-11, Jan-Pieter Cornet <joh...@xs4all.nl> wrote: > On 2011 Feb 11, at 13:54 , Jan-Frode Myklebust wrote: >> For us it took down clamd on 15 servers at 00:03 today, and >> we received the fix 3 hours later... but clamd wasn't restarter >> before later this morning, leading to huge mailqueues. >> >> We should probably look into verifying the db before telling >> clamd to reload it... > > I suggest you instead look at your mail config, verifying that mail > keeps on flowing when clamav happens to be down/unresponsive.
We fail over to using commandline clamscan, which means it keeps flowing, but apparently too slowly on our most busy servers. > > On the other hand, since you haven't updated ClamAV in over a year, > leading to (significantly) decreased detection, maybe the scanning of > email isn't top priority, and your mail scanning engine needs to > fallback to letting mail through on scan errors. > We have a strong preference to running only RHEL5+EPEL packages, so we're kind of stuck on 0.95.1 until EPEL updates or we move to RHEL6+EPEL which gives us clamav-0.96.1. I expect you will have quite a few users with the same/similar policy... Oh.. and freshclam said not to PANIC! ;-) -jf _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
