René Berber writes:
> > at which point the CPU falls back. the memory footprint of clamd
> > also seems to increase: after about an hour (wall clock) top
> > claims it's 95-100MB. CPU usage at the same time is 81 minutes --
> > about 1/3 of the total available. kinda sorta.
>
> Something is
-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
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:
[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:
> > ./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:
> > Did you build the package? What options did you used?
>
> pretty vanilla:
>
> ./configure --prefix=/export/home/clamav --enable-milter
So it has libcurl which brings openssl... some problem reports had this, could
you try a
René Berber writes:
> > system: 4 CPU Sun E450, solaris 5.9, gcc 3.4.3
> [snip]
> > at the moment, i'm probably going to back out to 0.88.7. before i do,
> > are there any other suggestions folks might have as to things to try?
>
> Did you build the package? What options did you used?
pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rick Pim wrote:
> system: 4 CPU Sun E450, solaris 5.9, gcc 3.4.3
[snip]
> at the moment, i'm probably going to back out to 0.88.7. before i do,
> are there any other suggestions folks might have as to things to try?
Did you build the package? What
