What causes a spamd 3.2.5 child process to be terminated by receiving a SIGCHLD signal?
I've looked at the spamc and spamd manpages but there's no mention of them there. I can't remember seeing them discussed on this maillist either. My last month's logs show 7 of them and I can't work out what caused them to be sent. However, Jose Luis Marin Perez' system is seeing a lot of them - on the order of 10% of messages scanned are getting hit by them, though his seem to be connected with very long running scans. So, what do these signals mean and what should I do to my SA configuration to get rid of them. Martin
