I recently upgraded my Debian server to 'etch', and with it the latest
packaged ClamAV - 0.90.2-1~volatile1 from the debian-volatile repository.
Also upgraded to kernel 2.6.20.

Since this, I seem to find the memory use of clamd grows and grows. I've
seen it up to 175MB before I had to stop and restart it - it's already back
up to 82MB a few hours after the restart. It didn't do this with 'sarge',
2.4 kernel, and the earlier ClamAV for Sarge.

Is this usage abnormal? I see other remarks on the list about this version,
but haven't spotted anything for definite.

The machine concered is a 'User mode Linux' virtual machine, and as such is
rather tight on memory - 80MB ram + 256MB swap, so this consumption by
ClamAV is making it near unusable. I'm often getting socket-timeouts when my
exim4 mailer attempts to process email using the clamd socket - quite
possibly due to time to page in clamd?

I've seen some mention of patches to ClamAV on the list - they sounded more
related to high CPU use than memory, but in any case I usually try to stick
with Debian packages, rather than building my own.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

Reply via email to