<snip>
typically our mailrelays do run out of memory(1GB physical and 2Gb swap) after a few (maybe 10 to 15) minutes with the snapshots 20040113 and 20040119 under load
We see this problem as well. On a couple of servers (Fedora Core 1, kernel 2.4.22-1.2149.nptl) with reasonably high load - 10 - 50 mails/second, clamd will run happily, using about 12 MB RAM, before it jumps to eat all available memory, before we encounter an oom-situation.
We do not see this as often as you do - last few times has been 5 minutes, 3 hours, 4 hours and 17 hours apart.
There is nothing in the logs or anywhere to suggest what is happening.
Latest version we have tried is clamav-devel-20040129.
ok after setting up a complicated testbed I managed to capture a message which results in a 2GB(!) memoryallocation of the latest snapshot 02012004 in less then 3 seconds ...
unfortunatly I'm unable to forward the offending message (confidental information of a costumer) - but I can provide debugging output and any assistence necessary to fix this to any developer requesting it in private!
Stefan
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
