[In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: Apache hangs, a lot of perl proccesses State-Changed-From-To: feedback-closed State-Changed-By: stoddard State-Changed-When: Tue May 25 08:41:30 PDT 1999 State-Changed-Why: I am closing this PR as a dup of PR 3168, even though I don't think this an Apache problem directly. Someting is wrong with one (or more) of your perl scripts (or the interpreter) which is preventing the proccess from exiting gracefully. This will eventually cause all your Apache threads to be blocked waiting on these errant perl processes to complete. With the fix I have in mind, Apache will kill off misbehaving CGI processes.
