Justin Mason wrote: > Dennis Duval writes: >> 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. > > You are restarting spamd after restarting syslogd, right? > spamd logs via syslog. If syslogd is restarted, it may > cause trouble for spamd, because its current connection > to syslog is now dead. > I have to restart spamd within a couple of minutes after restarting syslogd with the init script or it will crash the system. However doing a killall -HUP syslogd has no affect on spamd and it continues logging. I know of no other applications that would crash a system as a result of a syslog restart, but then not many applicationss are going to spawn processess as fast as spamassassin does on a high volume mailserver. Its not that big of a problem to use -HUP instead of the restart script during log rotation, etc.
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
