i am running .83, clamav-milter w/o clamd, freshclam on slack 9.1.
low load, but persistent flow of incoming messages ( a few hundred mails 
a day, no bad peaks).

normally, shortly after a successful freshclam update, clamav milter logs 
a 'loading new database' message and the x-virus-scanned line is updated, 
accordingly.

the 761 update (by freshclam) happened here at 2005-03-10-22.25.59 cet; 
the update was successful (checked by sigtool -i).

but in the hours passed by since, clamav-milter doesn't seem to have seen 
the new version; no 'loading new database' was logged, and the 
x-virus-scanned line still reflects the 760 version.

as this is happening for the first time: am i doing something wrong?
and: how can i 'force' clamav-milter to reload the new database?

tia!

-- 
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

Reply via email to