For the record I just want to say that I think "using excessive memory" is more correct than "memory leak".
The reason I thought clamd had a memory leak was because I'd run it under softlimits (set to say 40M) and clamd would end up (after mins,hours or days) hung at 39xxxM. The logs would show it to be in an infinite loop - attempting to malloc more RAM but being stopped due to the ulimit. I then upped it to 130M - the highest I was willing to go (not even Squid in our environment uses that much RAM!) and it would still happen. So I thought "memory leak" However, I loved clamd so much that I decided not to run it under softlimits, and - three months later - the darn thing still works 100% fine :-) So yes - it does seem to leap up to large amounts of RAM on occassion, but it does come back down - and it stops LOTS of viruses on our e-mail servers. We use it under Qmail-Scanner in conjunction with two commercial AVs. ClamAV gets called first, and if it thinks the message is CLEAN - then the other two get a go. So far ClamAV has caught ALL viruses - the only ones that it missed (and were caught by one of the other two) have so far all been corrupted viruses (there have been so few I checked by hand). ClamAV rulz. :-) -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 ------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
