>As far as I can figure out, from running clamscan on a
>large number of zip-files, archives which use the
>"deflated" type of compression work ok. Archives with
>compression types of "shrunk" or "imploded" will fail.
Looking at the sources I can see that the only compression
methods supported are
On Mon, 2004-11-22 at 14:54 -0500, Chris Gauch wrote:
>I've had the exact same problems with ZIP MODULE FAILURE
>ERRORS appearing intermittently throughout my clamd.log.
>The problems also began around that same timeframe
>(approx. 2 weeks ago). I haven't done too much in terms of
>debugging, etc.
Reply to the message of Monday December 15, 2003 21:57 +0100
-
On Mon, 15 Dec 2003 21:57:00 +0100
Tomasz Kojm <[EMAIL PROTECTED]> wrote:
>>From the clamd debug output:
>Do you have some logs for this crash ?
Sorry, it went to the /t
Reply to the message of Friday December 12, 2003 18:36 +0100
-
> >Every time the virus database is updated (by freshclam)
> >clamd will abort with a segmentation fault. What I see in
> >clamd.log is typically this:
>Thank you for the
Reply to the message of Thursday December 11, 2003 11:07 +0100
-
>Every time the virus database is updated (by freshclam)
>clamd will abort with a segmentation fault. What I see in
>clamd.log is typically this:
Since I've not had any
Hello,
I have been running clamd (0.65) on our mail server (Red Hat Linux
8 with kernel 2.4.20) for a few months without any problems at all.
Recently I decided to include Dazuko support in the kernel and
enable Clamuko in clamd.
This is up and running and works just fine apart from one problem.
