Well, still no luck, same errors over the weekend. Anybody have any other ideas?
Thanks,
Ben
On 22 mrt. 2013, at 18:43, Ben Stuyts wrote:
>
> On 22 mrt. 2013, at 18:29, David Raynor wrote:
>
>> On Fri, Mar 22, 2013 at 1:11 PM, Ben Stuyts wrote:
>>
>>> Hi,
>>>
>>> I was using clamscan for
daily.cvd is still here on 63 after doing this "fix"
note that the url says 73, so is it fixed now ?
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
Matt Olney skrev den 2013-03-22 18:49:
Yep, we've heard that a couple of times. We'll do our best to
address it.
being on clouds with sigle user clamd is waste of ram :)
i find this very funny that a cloud service cant provide cloud service
with clamd
are clamd not powerfull enough yet ?
Rick Macdougall skrev den 2013-03-22 14:56:
Ignoring mirror x.x.x.x (has connected too many times with an
outdated version)
and freshclam says dont panik :=)
imho as long clamd supports all signatures in cvd files there is no
need to update to latest clamav, but it might be needed this time
Ever since I updated "clamav" the other day, the "freshclam.log" has
been filling up with the following.
Sun Mar 24 06:43:43 2013 -> Received signal: wake up
Sun Mar 24 06:43:43 2013 -> ClamAV update process started at Sun Mar 24
06:43:43 2013
Sun Mar 24 06:43:43 2013 -> main.cld is up to date (v
