http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4304
------- Additional Comments From [EMAIL PROTECTED] 2006-10-03 23:52 ------- So it turns out that that patch doesn't help in my case. I can sort of repro the condition by inserting an exit(0); right before the server-side of the fork returns from spawn(). The funny thing is that if you look at the code we die() if we can't unblock the signals. In other words, if we can't unblock the signals we dump right into this condition :-) Thinking of it that way I can't quite understand why the signal blocking is there at all. I have a version of spamd here that removes all of it. Doesn't help this particular case but may be worth putting in anyway? Watching the logs as carefully as possible it appears that the bug occurs when the spamd parent is killed but the kill_handler is not called. In other words, if I know the parent is dead but I don't see a "spamd: server killed by SIG$sig, shutting down" line in the logfile I know with some certainty that I have orphaned children. This can be reproed by setting the INT handler for the parent to default. A very unlikely scenario is that the child signal setup is being called in the parent. I have little idea what's causing this. Can we just rewrite spamd? :-) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
