[clamav-users] A workaround for the major ClamAV DB update delays we have been experiencing
clamav-users at iment.com
Mon Dec 10 21:34:55 EST 2018
We ARE using freshclam to perform the actual update. And always have
We've only been using curl (not wget, if that matters) to pull the first
few bytes of the cvd to see if its version number matches what the DNS
TXT query said.
We do this because, after the conversion to Cloudflare, we were getting
lots of FAILURES where *freshclam* said things were out of sync (and
eventually disabled all the mirrors).
And we have recently seen that our Web server sometimes can get the new
updates (from IAD) *hours* before our main LAN does (from BOS).
P.S. It's been quite frustrating getting some replies seemingly based on
assumptions that we are doing things we shouldn't, when we aren't in
fact doing those things. (Like not using freshclam.)
On Mon, 10 Dec 2018 16:46:42 -0800
Dennis Peterson <dennispe at inetnw.com> wrote:
> Exactly right. We can't be blaming the ClamAV process when we don't
> use the ClamAV process. People that don't use freshclam should have
> no expectation of high reliability. In fact any expectations are
> baseless when the wrong tools are employed.
> On 12/9/18 5:44 AM, Joel Esler (jesler) wrote:
> > As it should be. No one should be downloading the daily and main,
> > (although thousands are), cdiffs were created for a reason.
> > Sent from my iPhone
> >> On Dec 9, 2018, at 06:58, Eric Tykwinski <eric-list at truenet.com>
> >> wrote:
> >> From back in archives, I think he’s using wget to just pull the
> >> files, but freshclam would just pull the cdiffs and keep you up to
> >> date on the next check.
More information about the clamav-users