The freshclam daemon process died the other day, and the last entry in
my log looks like:

ClamAV update process started at Wed Feb 18 06:51:56 2004
ERROR: Can't connect to port 80 of host database.clamav.net
(193.1.219.100)
ERROR: Connection with database.clamav.net (IP: 193.1.219.100) failed.
Trying again...
ClamAV update process started at Wed Feb 18 06:55:06 2004
ERROR: Maximal time (1200 seconds) reached.

I'm running 0.67-1. Is there any way I can make freshclam recover a bit
more gracefully than just dying? (or is it a bug?) 

I tried browsing the config for a way to set the "Maximal time" thing to
a higher number, but didn't find anything. The only solution I could
think of was adding a command to restart the daemon in the
'OnErrorExecute' section in the config, but I'm not sure that's very
clever either... (I guess the update server is busy at times, and
restarting every time freshclam can't connect will only add to the
hammering of the server).

Cheers,
--
Tarjei



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to