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
On Mon, 15 Dec 2003 09:08:00 +0100
Anders Herbjørnsen <[EMAIL PROTECTED]> wrote:
> >From the clamd debug output:
>
> LibClamAV debug: in cli_cvdload()
> LibClamAV debug: MD5(.tar.gz) = 3ebaf54c909410a2c1d2db61cb388cd7
> LibClamAV debug: in cli_untgz()
> LibClamAV debug: Unpacking /tmp/58259f93c7f
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
On Fri, 12 Dec 2003 10:27:57 +0100
Anders Herbjørnsen <[EMAIL PROTECTED]> wrote:
> 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
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.
