Since clamd in 0.65 is much too unstable here (stops responding within minutes), we have been running several development snapshots here. all the snapshots from the last 14 days or so seem to massivily leak memory. 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 . 20040104 behaves much better allthough it does seem to leak ~100MB/hour too. We do have some significant load here at times and we have ScanMail-Support enabled but in this state clamav/clamd is clearly quite unusable :-((
since there are quite a few of these problems popping up in the last days - any idea what can be done to fix or at least improve this situation?
In case it's important we are on Debian Woody 3.0r2 and Kernel 2.4.24 here.
Solaris 9, Netra T1 ultrasparc, clamav .65, compiled with gcc 3.3.2:
8 R qscand 3046 1 1 60 20 ? 4885 Jan 09 ? 396:45 /usr/local/sbin/clamd
38 megs of ram. hasn't changed significantly since starting it 12 days ago.
i think you may have other problems. what compiler are you using, and what optimization options?
Paul Theodoropoulos http://www.anastrophe.com
------------------------------------------------------- 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
