http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4703
------- Additional Comments From [EMAIL PROTECTED] 2005-11-23 00:29 ------- I'm under the impression my email didn't get here .. ok, this was the reply ... > Interesting, I've been seeing occasional signs of this on my medium loaded > server. How long have you been testing this patch? about 3 weeks. I had posted something about it in the ml, and wrote the patch right after. Before the patch, on some machines, I had to manually kill spamd about once a day, freeing up about 300/400 M of memory. Since the patch has been put in production (about 11 servers), this problem completely disappeared, and haven't seen other oddities. (hope it's just not me not being able to notice them) > I'd like to get this into 3.0.5 if the spamassassin developers deem it safe. sorry, you're right, it is version 3.0.2. On my Debian system, it is in /usr/share/perl5/Mail/SpamAssassin/Dns.pm. I had this problem on 3.0.4 on another machine too. The provided patch applies cleanly on 3.0.4 too. I usually do something like: cd /usr/share/perl5/Mail/SpamAssassin/ patch -p1 < patch.diff Probably, the sleep(1) in the patch could be replaced by something smarter, but I'm not too confident about adding more code in the alarm signal handler. Hope it is not debian specific. Hope it helps, if you need further details, I'm here :) If I can be of any coding help, just let me know... Cheers, Carlo ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
