This is on Linux,
[EMAIL PROTECTED] clamav-0.80]# uname -a
Linux krypton 2.6.8-1.521 #1 Mon Aug 16 09:01:18 EDT 2004 i686 i686 i386
GNU/Linux
[EMAIL PROTECTED] root]# freshclam
ClamAV update process started at Sun Nov 7 21:19:48 2004
main.cvd is up to date (version: 27, sigs: 23982, f-level: 2,
Fajar A. Nugraha wrote:
Just a hunch, I think you might have some old library (libclamav.so)
hanging around from 0.75.1,
maybe in /lib, /usr/lib, or /usr/local/lib.
I believe gentoo users can simply `emerge clamav` to install 0.80.
Regards,
Fajar
That was it! Thanks :)
I'd been emerging to insta
Daniel Kasak wrote:
Tamouh H. wrote:
Why don't you try without the flags
I just tried with only -march=i686 and I still get the same error (
undefined symbol: cl_build ).
What OS ?
Gentoo.
Just a hunch, I think you might have some old library (libclamav.so)
hanging around from 0.75.1,
may
Tamouh H. wrote:
Why don't you try without the flags
I just tried with only -march=i686 and I still get the same error (
undefined symbol: cl_build ).
What OS ?
Gentoo.
--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2
Hi,
I got these errors on Linux Console running ClamAV 0.80 :
LibClamAV Error: cli_calloc(): Can't allocate memory (131282 bytes).
calloc_problem: Cannot allocate memory
LibClamAV Error: cli_calloc(): Can't allocate memory (131282 bytes).
calloc_problem: Cannot allocate memory
LibClamAV Error: c
Why don't you try without the flags
What OS ?
Tamouh Hakmi
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Daniel Kasak
> Sent: November 7, 2004 10:10 PM
> To: [EMAIL PROTECTED]
> Subject: [Clamav-users] undefined symbol: cl_build
>
> Hi all
Hi all.
I just tried version 0.80 ( upgrading from 0.75.1 ) and I'm getting the
following error when I start clamd:
clamd: symbol lookup error: clamd: undefined symbol: cl_build
I compiled with the following cflags:
-march=athlon-xp -O3 -pipe
Any ideas?
Dan
--
Daniel Kasak
IT Developer
NUS Consult
Hi all,
I have setup clamav-milter from the crashhat repository and have it
running on FC2 along with spamassassin. Everything is working great,
and I can see in the log for clamd that I am detecting mail, and my
test recipient is not getting virus tests through. So it worksm, except
I'd like
Hello,
In the documentation it also mentions you can run clamd supervised, but the
director pointing to it: /doc/clamd_supervised/ is empty. This is available
under the FAQ section
How do I automatically restart clamd when it dies?
Set up a cronjob which checks that clamd is up and running, eve
On Sunday 07 Nov 2004 7:37 pm, Tamouh H. wrote:
> Hello,
>
> This had happened twice in the past two nights. I've had ClamD crash
> everynight after midnight.
>
> The first time, it crashed at 6 am on NOV 5th (there were no Crons running
> at that time).
>
> The second time, it crashed right during
I started the CLAMAV log and here is what I have so far:
Sun Nov 7 14:15:14 2004 -> +++ Started at Sun Nov 7 14:15:14 2004
Sun Nov 7 14:15:14 2004 -> clamd daemon 0.80 (OS: freebsd4.10, ARCH: i386,
CPU: i386)
Sun Nov 7 14:15:14 2004 -> Log file size limited to 2097152000 bytes.
Sun Nov 7 14:
Hello,
This had happened twice in the past two nights. I've had ClamD crash
everynight after midnight.
The first time, it crashed at 6 am on NOV 5th (there were no Crons running
at that time).
The second time, it crashed right during the freshclam update at 3:19 am on
NOV 6th.
I'm using FreeBS
>From Jason Frisvold
> I decided to run all of the tests located at testvirus.org against my mail
> server. As expected, tests 24 and 25
> got through, no surprise there.
> However, test 17 also made it through. This test is described as follows :
>Test #17: Eicar virus hidden using the "CR V
Nigel Horne wrote:
> On Saturday 06 Nov 2004 23:51, Christopher X. Candreva wrote:
>
> > You know what ? the people constantly saying "Don't hijack threads" is
> > far more anoying then the hijacked threads.
>
> What's even worse, it goes against one of the oldest netiquette sayings
> "priase in
On Saturday 06 Nov 2004 23:51, Christopher X. Candreva wrote:
> You know what ? the people constantly saying "Don't hijack threads" is far
> more anoying then the hijacked threads.
What's even worse, it goes against one of the oldest netiquette sayings "priase
in public, condem in private", so t
15 matches
Mail list logo
