Wilson Mak wanted us to know: >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). -- Regards... Todd They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. --Benjamin Franklin Linux kernel 2.6.3-15mdkenterprise 2 users, load average: 0.00, 0.01, 0.00 ------------------------------------------------------- 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
