https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5950
--- Comment #17 from Sidney Markowitz <[EMAIL PROTECTED]> 2008-08-06 11:21:02 PST --- (In reply to comment #15) Tom, What Justin said. I did test it by commenting out the signal and killing the child, and waitpid() does detect that correctly. > you could perhaps get rid of the timeout altogether (no > need to just give up on slow systems if they are still going) The timeout is supposed to be long enough that if you hit it something is wrong and you are better off getting a warning message and continuing in case the child process is actually running ok and the problem was just with the signal. That's supposed to be better than having the script that calls spamd hung up indefinitely. If you have experience that real heavily loaded systems take longer than 30 seconds to start up spamd I can increase the number. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
