Hi Todd,
On some ocassion, clamscan will stick ifself to the background and do
nothing - just eat up CPU resources. And also, the scanning message
will stay in the /var/spool/qmailscan/tmp/ and
/var/spool/qmailscan/working/new and the the process will then be
stopped there.
Any clues how to fix this?
Are you using clamscan or clamdscan? If you are using clamscan, your
memory usage will be very high. If you are using clamdscan, it's just a
wrapper that passes it to clamd which is not memory limited by softlimit
(unless you feel like adding it to the init script).
Thanks for your prompt reply. I am using clamscan. Initially, I set the
softlimit to 15000000 and it always got the error messages "Can't
re-allocate memory to xxx bytes". And then I set it to 18000000, it
reduces lots of these error messages - but still got some. So I try
increasing it to avoid getting these errrors. Perhaps, what is the best
value of softlimit if my box got 512M RAM.
Many thanks,
Wilson
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
