On Wed, 2005-11-16 at 09:27 -0500, Dale Blount wrote: > Hi List, > > Every few months or so when a new clamav comes out, I go to update all > of my servers to the latest version. The last few updates have caused > me a little grief because on restarting of clamd/freshclam, it reports > that freshclam wasn't running. This time I remembered to check before > upgrading. This is on one host (of about 10) running Linux 2.6 and > 0.87. Most upgrades anywhere from 2-4 of the 10 hosts have a dead > freshclam.
On closer review, there are 4 more hosts with out of date cvd files but freshclam is still running (but braindead). 3 of the hosts had the exact same size/date output: -rw-r--r-- 1 clamav clamav 149286 2005-11-04 08:50 daily.cvd -rw-r--r-- 1 clamav clamav 2560365 2005-11-04 08:50 main.cvd the 4th host had this: -rw-r--r-- 1 clamav clamav 102909 2005-10-14 04:02 daily.cvd -rw-r--r-- 1 clamav clamav 2560365 2005-09-16 11:34 main.cvd This makes 5 of 8 systems where freshclam stopped being functional. 2 of the 4 above needed kill -9 to die, the other 2 died on a normal kill signal. Is the general consensus to follow Dennis Peterson's suggestion and run freshclam from crond? That seems more like a work around than a fix, but I appreciate the option. Dale _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
