I'd like to let everyone know that there's a possible bug in
qscanq-0.43(scanning harness for qmail) after trying to use clamdscan
from
clamav-0.90.1 as the scanner. Downgrading to qscanq-0.42 resolved the issue.
This is the first time I've tried upgrading qscanq from 0.42.
___
René Berber writes:
> > ./configure --prefix=/export/home/clamav --enable-milter
>
> So it has libcurl which brings openssl... some problem reports had this,
> could
> you try a recompile w/o curl?
i can.
i tried a build with
./configure --prefix=/export/home/clamav --enable-milter --wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rick Pim wrote:
[snip]
> ./configure --prefix=/export/home/clamav --enable-milter --without-libcurl
>
> with ScanArchive yes in clamd.conf, it starts and seems to be scanning
> okay. CPU usage seems a lot 'spikier' than 0.88.7 with peaks at 80% or
René Berber writes:
> Something is very wrong there, after 1 day running I have clamd
> using only 32M of RAM (30M RSS). How many clamd threads do you
> see?
via ps -efL? or another mechanism. i'll check; i don't know if i'll
get a chance to do it this afternoon -- three day weekend coming u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rick Pim wrote:
> René Berber writes:
>
> > Something is very wrong there, after 1 day running I have clamd
> > using only 32M of RAM (30M RSS). How many clamd threads do you
> > see?
>
> via ps -efL? or another mechanism. i'll check; i don't
Since updating to 0.9x I have noticed that from time to time after a
cdiff update via freshclam, clamd reports a much smaller value for the
number of signatures than freshclam. Some number of updates later
the two then match again.
Can someone explain what is happening here? Freshclam is correctly
