On Mon, Apr 19, 2004 at 10:17:37AM -0400, Joe Maimon wrote: > If you use any resource limiting or are running up against low memory, > expect clamav to segfault when it runs out of memory resources.
Yes, I expect that, but: 1> why would clamd need to grow to 50M of RAM? I also run Sophie (for Sophos) and Trophie (for Trend) and both those daemons stay around the 10-15M RAM mark. This smells of a memory leak to me... 2> If clamd segfaults, then it *doesn't* exit - so all further invocations of clamdscan hang. That is a bug too. If clamd segfaults, then shouldn't it cleanup and exit? If it is a child that segfaults, then why does that affect the rest of the clamd processes? (ah: threads - I forgot...) -- 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: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
