Noel Jones wrote:
To make yours less sensitive to transient failures, you can change it to:
if failed host 127.0.0.1 port 3310 type tcp protocol clamav
timeout 30 seconds 2 times then restart
I'm aware of the timeout and times options, I consider them to be
workarounds as well. I was
At 09:21 AM 1/24/2007, Aleksander wrote:
Hi,
Got a little problem.
I've noticed that sometimes clamd is restarted by monit (monitoring software).
monit is configured like this:
check process clamd with pidfile /var/lib/clamav/clamd.pid
start program = "/etc/init.d/clamd start"
stop pr
Aleksander wrote:
So the big question:
How does clamav answer to a PING while updating/loading the virus db?
or
How do we detect, that clamd is not dead, but simply updating it's
database?
For now, I'll simply disable the clamav protocol test and stick with
only checking the INET socket. B
Hi,
Got a little problem.
I've noticed that sometimes clamd is restarted by monit (monitoring
software).
monit is configured like this:
check process clamd with pidfile /var/lib/clamav/clamd.pid
start program = "/etc/init.d/clamd start"
stop program = "/etc/init.d/clamd stop"
if
