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

2018-10-20 Thread Joel Esler (jesler)
Well the TXT based approach is to tell you (the users) when to update. It’s a decent approach, and any change to that would be a good amount of work. Which we’re not against, it’s just a baby step. It also means, (which may be a good thing?) we’d have a departure between “people who keep ClamA

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

2018-10-20 Thread Paul Kosinski
Yes, file synchronization is difficult. But we *started out* using the provided (i.e., standard) freshclam tool to update our daily.cvd (etc.). I only built our current non-standard tool (reading the file header) when the Cloudflare mirrors started serving out-of-date file versions which caused fre

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

2018-10-20 Thread Joel Esler (jesler)
Right Dennis. There will always be a delay, I can’t get it down to zero. But I can minimize it. That being said, the infrastructure we are using today is a ton more reliable than the previous mirror infrastructure. Sent from my iPhone > On Oct 20, 2018, at 09:58, Dennis Peterson wrote: >

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

2018-10-20 Thread Dennis Peterson
Caching file systems do validate the requested file against a master file to see if there has been a change. De-dupe caches do the same. It isn't instantaneous but they also don't have to wait for the cache to refresh as they can deliver a pass through request at the same time they're updating t