freshclam (0.80) as compiled from ports on a FreeBSD 4.10 box seems to run
on it's own for a period of time, then although the process is still alive,
just seems to stop doing any work.  Witness the below, set to check 48 times
a day, or once every 30 minutes, performs one check, then does nothing.
Typically this dies during the night but I was able to get it to reproduce
this morning with just one check.  I started it at 9:32AM, by 11:51AM it had
only done one check that I can see.  Duplicate lines are the result of me
tailing the log files while also running the command in verbose mode.  Any
ideas why it hangs?  Is it checking but not logging or telling me?

wmail1# freshclam -v -c 48
--------------------------------------
Current working dir is /var/db/clamav
Max retries == 3
ClamAV update process started at Wed Jan 12 09:32:03 2005
ClamAV update process started at Wed Jan 12 09:32:03 2005
TTL: 801
main.cvd version from DNS: 28
Software version from DNS: 0.80
main.cvd is up to date (version: 28, sigs: 26630, f-level: 3, builder:
tomek)
main.cvd is up to date (version: 28, sigs: 26630, f-level: 3, builder:
tomek)
TTL: 801
daily.cvd version from DNS: 663
Downloading daily.cvd [*]
daily.cvd updated (version: 663, sigs: 2780, f-level: 3, builder: ccordes)
daily.cvd updated (version: 663, sigs: 2780, f-level: 3, builder: ccordes)
Database updated (29410 signatures) from db.ca.clamav.net (64.69.64.158).
Database updated (29410 signatures) from db.ca.clamav.net (64.69.64.158).
SelfCheck: Database modification detected. Forcing reload.
Clamd successfully notified about the update.
Clamd successfully notified about the update.
Freeing option list...done
wmail1# Reading databases from /var/db/clamav
Database correctly reloaded (29410 viruses)
SelfCheck: Database status OK.
Reading databases from /var/db/clamav
Database correctly reloaded (29410 viruses)

wmail1# 
wmail1# date
Wed Jan 12 11:51:06 EST 2005

--
Jason 


_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users

Reply via email to