Thanks for the follow up, but this appears to be a one-off here as well.
It's all working fine at the moment.
Happy New Year
Bill
-Original message-
> From:Orion Poplawski
> Sent: Tuesday 1st January 2019 13:38
> To: ClamAV users ML ; Bill Maidment
>
> Subject: Re: [clamav-users] Probl
On 12/30/18 7:24 PM, Bill Maidment wrote:
Hi
I have just updated clamav to 0.101.0 from EPEL and I got the following error.
Maybe this is a one-off. Anyone else seeing this? Or do I have a configuration
issue?
Cheers
Bill
-Original message-
From:(Cron Daemon)
Sent: Monday 31st Decem
Perhaps the distro people (RH/Centos) tried to compensate for the
missing headers -- so other software could use libclamav etc. -- and
introduced a bug?
On Mon, 31 Dec 2018 14:49:51 +
"Micah Snyder (micasnyd)" wrote:
> I don't think this would be related. The missing headers issue would
>
I don't think this would be related. The missing headers issue would prevent
others from compiling projects that depend on clamav and wouldn't result in
runtime errors such as the one Bill is reporting.
I haven't seen this bug before. The backtrace doesn't have symbols/function
names so it's rea
I am running CentOS 7 and just updated to 0.101.0 from EPEL on 2
servers. This might be related to the same issue as above, but after
upgrading, I got the same freshclam error as the person above on 1
server, but my 2nd server ran out of disk space overnight. I noticed
a directory was created
/va
