Morris Jones wrote: > I've never had a problem like this, of course. But I > wonder what you might discover if you turned debugging on > for spamd? Start it with the -D flag? > Thanks to Justin Mason and Tom Meunier for pointing out the -m option and the FAQ on this questions. Last night, I removed my supervisor script for spamd and ran spamd with a -m 20 option. It ran just fine overnight, but this morning I did an "/etc/init.d/syslog restart" and immediately the number of processes began to soar. Within 1 minute there were 24 running spamd processes, with it totally ignoring the -m value. So I killed and restarted spamd and set my supervisory script back to watching spamd.
I have had debugging turned on during a couple of these events, and spamd seems to be working fine up to the moment it runs out of memory, then it stops logging. I have determined with pretty good confidence that it does not have anything to do with incomming mail load. I have spent hours pouring over qmail logs to find some correlation. Then when I found out that I could cause the event simply by running my syslog init script using the 'restart' option, I became convinced that it is a bug, either in spamassassin or in syslogd, or something screwy in my system configuration. The event is very repeatable, and is not at all related to mail volume. It appears to me that something is keeping spamd instances from terminating. Since this is a fairly high-volume server, it just takes seconds for all the memory to be eaten up by spawning-but-not-terminating spamd processes. Dennis Duval ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
