Hello Brian Morrison, > I presume that the action of uploading a new database update triggers a > script that: > > sends the mailing list notification > updates the database on the main (non-public) server > kicks off a DNS update
correct > but may not: > tell mirror servers to re-sync with the main server it does. > There is also the question of your own DNS access and caching behaviour, precisely. This matter has been discussed _many_ times. In short: - the TTL of current.cvd.clamav.net is 900 secs - if you run freshclam (with DNSDatabaseInfo) more often than 900 secs, you just overload _your_ dns. - if you disable DNSDatabaseInfo and run freshclam more often than every 30 minutes, you'll seriously damage the performance of our mirrors - please understand that if everyone were to download the database _as soon as_ it's uploaded to the mirrors (which happens _before_ we send the message to the ml), most mirrors wouldn't be able to handle the requests. Calling freshclam when a new message from clamav-virusdb@ arrives is silly. By implementing DNSDatabaseInfo, we spread the downloads over a time frame of 15mins and make silly setups fail <evil g> Best regards -- Luca Gibelli (luca at clamav.net) - ClamAV, a GPL virus scanner PGP Key Fingerprint: C782 121E 8C3A 90E3 7A87 D802 6277 8FF4 5EFC 5582 PGP Key Available on: Key Servers || http://www.clamav.net/gpg/luca.gpg _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
