At 11:20 AM 8/31/2007, Gerard wrote: >On Friday August 31, 2007 at 12:05:58 (PM) Dennis Peterson wrote: > >[snip] > > > A proper script will send clamd a reload command on completion of > > downloading, testing, and distributing third party files. This can be as > > simple as sending kill -USR2 to the clamd PID, or using either the clamd > > tcpip or Unix socket to send a reload command. > >You are misreading the question. I never said anything about manually >forcing a reload of the data base. I am inquiring as to why clamav no >longer seems to be checking and reloading the signature files on its >own. The clamd.log shows an entry "Self checking every 1800 seconds"; >therefore I am sure that the clamd daemon is aware of that setting. >For whatever reason, it does not appear to be observing it though. I >am not sure, but I believe the older versions of clamav did not have >this problem. At least I do not remember it.
Just try it. It works for me. In fact, clamd seems to reload almost immediately when an existing *db is altered. # date Fri Aug 31 11:33:35 CDT 2007 # cd /path/clam/db (assuming you have the SaneSecurity signatures) # touch phish.ndb (wait a couple seconds) # tail /path/to/clamd.log ... Fri Aug 31 11:34:00 2007 -> WARNING: Database has changed, loading updated database Fri Aug 31 11:34:01 2007 -> Loaded ClamAV 0.91.2/4111/Fri Aug 31 10:25:39 2007 Fri Aug 31 11:34:01 2007 -> ClamAV: Protecting against 181015 viruses Yes, this is repeatable and works no matter which *db is touched. This is clamav 0.91.2 on FreeBSD on a (not particularly busy) mailserver. -- Noel Jones _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
