It's because their mirrors are extremely slow and they won't add any new
mirrors. What you are waiting for is for a mirror to timeout (30sec)
before it will move onto the next mirror. And so on...
I routinely go through 5 or 6 mirrors before I find one that's active.
On Sat, Nov 12, 2016 at 1:55
ClamAV.
On Sat, Nov 12, 2016 at 5:19 PM, Joel Esler (jesler)
wrote:
> Who is “they”? Us? Or ClamWin?
>
> --
> Joel Esler | Talos: Manager | jes...@cisco.com<mailto:jes...@cisco.com>
>
>
>
>
>
>
> On Nov 12, 2016, at 5:02 PM, Rudy Stebih clamavmir...@gm
; >
> > --
> > Joel Esler | Talos: Manager | jes...@cisco.com<mailto:jes...@cisco.com>
> >
> > On Nov 12, 2016, at 5:02 PM, Rudy Stebih wrote:
> >> It's because their mirrors are extremely slow and they won't add any new
> >> mirrors. What you
uspect the ClamAV network folks could look into that if you can post a
> summary of the mirror sites that aren't working for you along with your
> geographic location and the results of running these commands:
>
> freshclam --list-mirrors
> host database.clamav.net
>
> -A
In the ClamAV-Mirrors mailing list it has been mentioned several times.
On Sat, Nov 12, 2016 at 6:16 PM, Al Varnell wrote:
> On Sat, Nov 12, 2016 at 06:02 PM, Rudy Stebih wrote:
> >
> > Clamwin & ClamAV are exactly the same engine. The ONLY difference is
> that
> >
Hi Folks,
I've been getting the following error for a week or so:
'LibClamAV Warning: Bytecode runtime error at line 1226, col 4'
I finally found the time to run ClamAV in verbose mode and believe this is
the culprit:
'Scanning C:\Program Files (x86)\Applian Director\ClearRegCode.exe'
At least
ow.
>
> Dave R.
>
> On Tue, May 2, 2017 at 10:05 PM, Rudy Stebih
> wrote:
>
> > Hi Folks,
> >
> > I've been getting the following error for a week or so:
> >
> > 'LibClamAV Warning: Bytecode runtime error at line 1226, col 4'
> &g
ation
Information\{1FA41DBD-E8F8-46B1-A90C-1FA7E823DA58}\ISSetup.dll
LibClamAV Warning: Bytecode runtime error at line 968, col 5
Cheers,
Rudy
On Sat, May 6, 2017 at 11:07 AM, Joel Esler (jesler)
wrote:
> I thought this was fixed.
>
> --
> Sent from my iPhone
>
> > On May 6, 2
