[clamav-users] We STILL cannot reliably get virus updates (since new mirrors)
dennispe at inetnw.com
Mon Jul 2 00:11:29 EDT 2018
What makes it a problem? You can never dl it until it is available, so the
problem is you become aware of it too soon. But think about what that means.
Your choices are to know immediately when an update is available and try to get
it, or wait until every mirror is synchonized, become notified, then try. The
first choice is a crapshoot you might win. The second choice isn't a crapshoot
but it also doesn't save time. Remembering all this is automated the result is
actually some uninteresting log entries.
It would be interesting to know if an update notice is sent to all mirrors in
the fashion of a DNS notification to slaves which would cause a parallel pull,
or if the update itself is pushed, and what the process is for updating the
client mirrors.dat file.
On 7/1/18 9:01 PM, Al Varnell wrote:
> Seems to me that it's only a problem if it takes a significant amount of time between the DNS update and the mirror updates. I don't have a good feel for how long that is from the postings so far, but it does sound like it may have increased as a result of the move from ClamAV mirrors to the ClamAV CDN.
> Sent from my iPad
>> On Jul 1, 2018, at 20:38, Dennis Peterson <dennispe at inetnw.com> wrote:
>>> On 7/1/18 8:24 PM, Paul Kosinski wrote:
>>> My conclusion is that the cause of this is a typical race condition:
>>> the DNS TXT record is updated before Cloudflare has propagated the new
>>> cvd file to all the mirrors.
>> Is this a problem?
>> clamav-users mailing list
>> clamav-users at lists.clamav.net
>> Help us build a comprehensive ClamAV guide:
> clamav-users mailing list
> clamav-users at lists.clamav.net
> Help us build a comprehensive ClamAV guide:
More information about the clamav-users