On 10/10/07, Robinson Craig <Craig.Robinson@xxxxxxxxxxxxxx> wrote: > Hi Folks, > > I'm a bit confused about the effects of changing the MaxRequestsPerChild > directive. > > I previously had MaxRequestsPerChild set to "0" which, as I have always > understood, means that there is no maximum. Last night I changed the > config to: > > MaxRequestsPerChild 100 > > And about an hour after a "hard" restart of Apache, I get the following > as an example of a typical server-status for the first 3 processes: > > Srv PID Acc M...etc > 0-0 6702 0/191/828 W...etc > 1-0 6735 1/210/780 K...etc > 2-0 6736 5/205/844 K...etc > > As I understand, the "Acc" column is made up of: # accesses per > connection/child/slot. Yet, the number of "Accesses" per each child is > reported as > 100. I would have thought that setting MaxRequestsPerChild > to 100 means that the process would be terminated after 100 requests (or > "accesses"), so that this number should never exceed 100. > > Can anyone shed any light on this? As the docs say http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxrequestsperchild MaxRequestsPerChild is actually a miss-named MaxConnectionsPerChild Joshua --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|