On 05/07/2010 02:25 PM, Luis Miguel R. wrote:
> El viernes, 07 mayo del 2010 a las 11:59:45, Toby Bryans escribió:
>> The very latest update causes the following debug output. A quick search on
>> twitter finds someone else with similar issues too.
>
> I have the same problem, using "ClamAV 0.95.3
On 7 May 2010 16:05, Christopher X. Candreva wrote:
> On Fri, 7 May 2010, Toby Bryans wrote:
>
> > The very latest update causes the following debug output. A quick search
> on
> > twitter finds someone else with similar issues too.
> >
> > @40004be3ecf5208b0ff4 LibClamAV debug: Initialized 0
On Fri, 7 May 2010, Toby Bryans wrote:
> The very latest update causes the following debug output. A quick search on
> twitter finds someone else with similar issues too.
>
> @40004be3ecf5208b0ff4 LibClamAV debug: Initialized 0.95.3 engine
> **
Toby Bryans wrote:
> On 7 May 2010 12:28, Per Jessen wrote:
>
>> Toby Bryans wrote:
>>
>> > Thanks Luca, I obviously should have checked there in retrospect!
>> >
>>
>> It was posted 8 minutes after your posting, so checking there
>> wouldn't have done you any good :-)
>
>
> :)
>
> I can conf
> See http://lurker.clamav.net/message/20100507.110656.573e90d7.en.html
Interesting. My OpenBSD-CURRENT-ish (32-bit) system loaded the flawed
update, but did not have issues. It's running 0.95.3 for the moment.
Fri May 7 03:27:19 2010 -> Trying host db.us.clamav.net (213.165.80.159)...
Fri Ma
On 7 May 2010 12:28, Per Jessen wrote:
> Toby Bryans wrote:
>
> > Thanks Luca, I obviously should have checked there in retrospect!
> >
>
> It was posted 8 minutes after your posting, so checking there wouldn't
> have done you any good :-)
:)
I can confirm that the latest update definitely wor
Toby Bryans wrote:
> Thanks Luca, I obviously should have checked there in retrospect!
>
It was posted 8 minutes after your posting, so checking there wouldn't
have done you any good :-)
/Per Jessen, Zürich
___
Help us build a comprehensive ClamAV g
El viernes, 07 mayo del 2010 a las 11:59:45, Toby Bryans escribió:
> The very latest update causes the following debug output. A quick search on
> twitter finds someone else with similar issues too.
I have the same problem, using "ClamAV 0.95.3/10939"
Regards.
___
Em 07-05-2010 08:19, Luca Gibelli escreveu:
Hello Toby,
The very latest update causes the following debug output. A quick search on
twitter finds someone else with similar issues too.
See http://lurker.clamav.net/message/20100507.110656.573e90d7.en.html
Best regards
Hi,
I ha
Thanks Luca, I obviously should have checked there in retrospect!
On 7 May 2010 12:19, Luca Gibelli wrote:
>
> Hello Toby,
>
> > The very latest update causes the following debug output. A quick search
> on
> > twitter finds someone else with similar issues too.
>
> See http://lurker.clamav.net/
Hello Toby,
> The very latest update causes the following debug output. A quick search on
> twitter finds someone else with similar issues too.
See http://lurker.clamav.net/message/20100507.110656.573e90d7.en.html
Best regards
--
Luca Gibelli (luca _at_ clamav.net) ClamAV, a GPL anti-v
The very latest update causes the following debug output. A quick search on
twitter finds someone else with similar issues too.
@40004be3ecf5208b0ff4 LibClamAV debug: Initialized 0.95.3 engine
@40004be3ecf5208c1d7c LibClamAV debug: Initializing phishcheck module
@40004be3ecf5208c448c L
12 matches
Mail list logo
