Dale Blount said: > 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. > >
I avoid that problem by running freshclam from cron by way of this script: freshclam.sh #!/bin/bash if [ -z "$1" ]; then sleep $[ RANDOM % 1800 ] fi /usr/local/bin/freshclam --quiet --daemon-notify=/usr/local/etc/clamd.conf exit The random statement ensures it doesn't contribute to a pile up at the freshclam servers and is recommended for anyone using cron with freshclam. If I run it manually with an argument "freshclam.sh now", for example, it will bypass the delay and immediately execute. I've found this to be far more reliable than the daemon and is one less process I need to continuously monitor. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
