Hello Dennis, thanks for the reply. Though I am far from being a ClamAV expert I was not aware the default config leads to 17 minutes after the hour(+2) for the DB update. All I can see possible is to edit freshclam.conf for:
################################################# # Run command when database update process fails. # Default: disabled #OnErrorExecute command # Number of database checks per day. # Default: 12 (every two hours) #Checks 24 ################################################# Then replace <command> with a script that changes the Checks 24 to Checks <random number between 0 and 24> and then issue a HUP to the freschclam daemon. Please reply with a more viable solution as I would not want to bound freshclamd at any kind of regularity. Thanks, David. Dennis Peterson wrote .. > da...@davidwbrown.name wrote: > > Hello aCaB, thanks for the informative and speedy reply. The command > > returns the expected TXT string. My clam updates 17 minutes after the > > hour every 2 hours. In about 40 minutes or so I will recheck the log > > and report back upon getting this error again unless you can suggest > > how-to proceed. Please advise, David. > > > > You might consider randomizing the times at which you check for > signatures so you don't dogpile on with everyone else who has hard-coded > 17 minutes past the hour. > > dp > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
