Re: general/3046: Apache letting child processes run too long

[ji...@apache.org]

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> 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 letting child processes run too long

State-Changed-From-To: open-closed
State-Changed-By: jim
State-Changed-When: Thu Jun 10 05:12:37 PDT 1999
State-Changed-Why:
MaxRequestsPerChild is actually max _connections_ per child. In other words, what we're seeing is the effect of keepalive requests. So the child is handling 11700 requests, for example, but only 10000 connections. The newer docs make this clear.