I have about eight mail servers running clamd, and since the last port
install/update of ClamAV from the FreeBSD ports tree, I'm noticing the
clamd process grow to HUGE huge sizes (500M within about 20 hours)..
Without paying much attention we noticed the process grow to several
GB in size until the kernel finally had enough and killed the process.
Starting them about 20 hours ago, I see the resident size of the clamd
process is over 600M and going again. I think previously after
several weeks the process was only 80-110M or so...
FreeBSD 6.4-RELEASE-p4 amd64
[cartman:~] pkg_info | grep clamav
clamav-0.95.1_1 Command line virus scanner written entirely in C
From top on four of the servers:
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
COMMAND
63792 clamav 3 96 0 682M 675M ucondt 1 9:22 0.34% clamd
56701 clamav 3 96 0 672M 664M ucondt 3 9:19 0.54% clamd
66809 clamav 3 96 0 698M 691M ucondt 3 9:38 0.39% clamd
66059 clamav 4 96 0 669M 662M ucondt 3 9:33 0.49% clamd
ldd:
/usr/local/sbin/clamd:
libclamav.so.6 => /usr/local/lib/libclamav.so.6 (0x80064d000)
libbz2.so.2 => /usr/lib/libbz2.so.2 (0x800820000)
libz.so.3 => /lib/libz.so.3 (0x800930000)
libthr.so.2 => /usr/lib/libthr.so.2 (0x800a44000)
libc.so.6 => /lib/libc.so.6 (0x800b5b000)
Only things we have from defaults in clamd.conf:
LogFile /var/log/clamav/clamd.log
LogFileMaxSize 0
LogTime yes
LogVerbose yes
PidFile /var/run/clamav/clamd.pid
TemporaryDirectory /var/tmp
DatabaseDirectory /var/db/clamav
LocalSocket /var/run/clamav/clamd
FixStaleSocket yes
MaxConnectionQueueLength 30
StreamMaxLength 20M
MaxThreads 20
ReadTimeout 60
User clamav
AllowSupplementaryGroups yes
ScanMail yes
PhishingSignatures yes
PhishingScanURLs yes
MaxScanSize 50M
MaxFileSize 30M
MaxFiles 5000
--
Robert Blayzor, BOFH
INOC, LLC
[email protected]
http://www.inoc.net/~rblayzor/
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
