da...@davidwbrown.name wrote: > 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 > ################################################# >
If you run it as a daemon then it lights off each 2 hours starting from when you started it - which for all users is likely a random time, of course, else it would truly be a dogpile at 17 minutes past. I presumed when you nailed it at 17 minutes past that you were not running it as a daemon but through a script. I run it in a script via cron, and the script does randomize the actual connect time. There may be some discussion on the ClamAV wiki regarding this. I found the randomization improved the connection success when I first installed it - there are more clients out there now so that may no longer be true. I haven't checked in the past year. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
