Sorry to reply to my own post, but I've found the problem:
On Wed, Oct 09, 2002 at 11:53:57AM -0300, Everton da Silva Marques wrote:
>
> Oct 9 10:01:31 itu amavis[1646]: Scanning with CLAM
> Oct 9 10:01:31 itu amavis[1646]: Output from /usr/local/clamav/bin/clamscan
> --stdout --threads 0 -r -
Hello.
We're running amavis-ng with Clam 0.24.
The upgrade to Clam 0.51 is failing with the following log from Amavis:
Oct 9 10:01:31 itu amavis[1646]: Scanning with CLAM
Oct 9 10:01:31 itu amavis[1646]: Output from /usr/local/clamav/bin/clamscan --stdout
--threads 0 -r -w
/var/amavis-ng/tmp/
On the 9th of October 2002 at 15:29, "Dave Sill" <[EMAIL PROTECTED]> wrote:
> I'm running 0.24 under Red Hat 7.2 and qmail-scanner 1.14.
same here, except i'm running debian woody.
my clamav is 'patched' with "#define MIN_LENGTH 3" in clamscan/matcher.h
> clamscan has been working fine for weeks
I'm running 0.51 under Linux 2.4.19
A clamd SCAN of this directory seems to work fine:
[EMAIL PROTECTED]:~# ls -lasd /home/jason/viruses
4 drwx--6 foo root 4096 Apr 22 14:38 /home/jason/viruses/
[EMAIL PROTECTED]:~# telnet localhost
Trying 127.0.0.1...
Connected to local
I'm running 0.24 under Red Hat 7.2 and qmail-scanner 1.14.
clamscan has been working fine for weeks with a 20,000,000 byte memory
limit. This morning--perhaps after the virus database was updated--I
started seeing the following error:
CRITICAL: Can't allocate memory (2064 bytes).
I raised the
> Now is the point where I am totaly confused.
> first I set ulimit -d 1 so 10MB, then
> I set a breakpoint in gdb to the calloc function.
> then after it reaches the function i do backtrace do you see how much
> memory the program tries to allocate at point #2 ?
I have limited memory usage i
Hi,
I just downloaded clamav-0.50, extracted it, did a ./configure, no
problems there. Then when I did a make, it complained about
treewalk.h:40: parse error before `*'
treewalk.h:40: warning: data definition has no type or storage class
make[1]: *** [clamscan.o] Error 1
make[1]: Leaving directo
