On Aug 23, 2006, at 9:42 AM, Karl Pielorz wrote:
Looking back at the logs - clamd typically consumes around 40Mb /
36Mb of memory (total / resident).
This is on a pretty busy server - something's happening to cause
that to baloon - e.g. when we catch in the throws of death it's
using around 600Mb RAM (of which 550Mb odd is marked as 'resident')
with the machine starting to swap heavily.
Clamd will grow as needed to handle any compressed files being passed
to it; perhaps someone is sending maliciously constructed archives
which require excessive resources to unpack and scan? clamd.conf
should have some tunable knobs related to this which you might try
adjusting. Also, I don't think that clamav-milter is the best
interface for doing virus scanning, but YMMV; consider using a
frontend like amavisd which invokes clamdscan as needed only after a
message passes less resource-intensive checking.
Note that /var/log/clamav/clamd.log might contain useful information...
--
-Chuck
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
