[clamav-users] Latest report on update "delays"

[Joel Esler (jesler)]

We are aware that fresh clam is part of the issue.  We are going to introduce some new code to freshclam (and have in the past two releases, IIRC) to prevent stuff like this happening.  More updates to freshclam will come in future versions as well.

That being said, it's important to realize that we will still have millions of users stuck on old version.  But there is only so much we can do for those people.

> On Oct 23, 2018, at 1:52 AM, Gary R. Schmidt <grschmidt at acm.org> wrote:
> 
> On 23/10/2018 16:17, Paul Kosinski wrote:
>> Two observations: First, a smoothly working freshclam mechanism
>> shouldn't require workarounds.
> Well, yes, but it works smoothly for a very large number of people, myself included.
> 
>> And I suspect many ClamAV users
>> wouldn't be able to deal with workarounds like this.
> This I disagree with - if they are bright enough to go looking for something like ClamAV then they'd be able to handle the trivial task of adding a line to a crontab file.
> 
>> Second, any time freshclam fails due to an out-of-sync problem, there
>> has been a useless load on the mirrors (although I suppose using cdiffs
>> would significantly reduce the useless data transfer). Plus there is
>> useless load on the client machine and its LAN.
> There is a load only on the mirrors you are accessing, the rest of them keep doing their job.
> 
> Have you absolutely ruled out the possibility of someone having set up a transparent proxy on your border router(s)?
> 
> 	Cheers,
> 		Gary	B-)
> _______________________________________________
> clamav-users mailing list
> clamav-users at lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml