http://bugzilla.spamassassin.org/show_bug.cgi?id=3443
------- Additional Comments From [EMAIL PROTECTED] 2004-05-29 17:00 ------- It appears that some of the time spamd (under Cygwin) is not catching the SIGTERM before the process is shut down, which leaves the child processes all running. Google found this post from 2001 to an Apache mailing list discussing a similar problem which is attributed to a bug in Cygwin's handling of SIGTERM when under high load: http://www.mail-archive.com/[email protected]/msg00466.html It says in part: [begin quote] yes, that effect is known to me. It seems Cygwin has problems with signal passing under high loaded or long-running processes. Usually Apache will try to use SIGUSR signal to gracefully shutdown the childs, if this fails for some defined timeout, the parent process (`cat <path>/logs/httpd.pid`) will send "stronger" singnals, so SIGTERM and SIGKILL are send, which then should shutdown the child processes. It takes some seconds to perform this, so that's why a "apachectl restart" usually fails, because it does not check if the processes have gone away before "starting" again. Usually it is eneough to $ kill -TERM `cat <path>/logs/httpd.pid` to stop all processes, which is in fact the same thing "apachectl stop" does. [end quote] No fix is mentioned. This is three years old, but I haven't yet found anything more recent abiout this. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
