|Main Archive Page > Month Archives > clamav-users archives|
Steve Basford wrote:
> Gut feeling is that it's not a signature problem, more timing perhaps
> caused by the increase in the number of signatures being reloaded,
> and the interaction between freshclam, the RELOAD/USR2 command (used by
> scripts) and clamd.
I don't have a problem here (yet, fingers also crossed) but I don't run freshclam as a daemon. It is run out of cron as is the script I wrote to refresh Sane Security signatures. I set them var enough apart they cannot collide.
I also use rsync to move the Sane Security files from the download/test directory into the clamav database directory as it does atomic copies. Clamd is not aware of them until rsync unhides them. The thinking is it makes them immune to clamd's self-check process. A self-check with a file partially copied to the db directory has caused clamd errors in the past.
So the sequence here is: