http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4304
------- Additional Comments From [EMAIL PROTECTED] 2006-10-02 15:27 ------- I think I've identified my problem: - external process starts up spamd - spamd blocks SIGINT - spamd forks off children - external process kills spamd parent, it dies nearly immediately - spamd children continue loading things up (this takes a while in our environment) - external process starts new spamd parent (after short pause) - external process chokes saying socket already in use - spamd children finish loading up, unblock SIGINT, receive SIGINT and then die Is there a reason to continue blocking SIGINT until the child is essentially fully ready to run? In my simple test case moving the unblocking of SIGINT to immediately after the fork() within the child process helps to make sure the child dies immediately and can't linger around for a while. I see that certain things get done with Bayes there and Michael Parker has expressed concern over corrupting databases. Are there actual concerns or reasons for keeping those signals blocked for so long? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
