Hi
I'm usinf clamav-0.68-1 and occasionally (once every two weeks) I get this response
ClamAV update process started at Tue Mar 30 08:46:36 2004 SelfCheck: Database status OK. ERROR: Maximal time (1200 seconds) reached.
Then the freshclam daemon died.
Anyone else come acroos this sort of behaviour?
Cheers Bill
I just noticed the same on one of my boxes running 0.70-rc:
--------------------------------------
Received signal 14, wake up
ClamAV update process started at Tue Mar 30 11:42:58 2004
main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder: tkojm)
ERROR: Maximal time (1200 seconds) reached.
--------------------------------------
freshclam daemon started (pid=2216)
ClamAV update process started at Tue Mar 30 18:05:54 2004
main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder: tkojm)
daily.cvd updated (version: 227, sigs: 428, f-level: 1, builder: diego)
Database updated (20657 signatures) from database.clamav.net (152.66.249.132).
Clamd successfully notified about the update.
-- Ryan Moore ---------- Perigee.net Corporation 704-849-8355 (sales) 704-849-8017 (tech) www.perigee.net
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
