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? Cheers, Craig ************************************************************************ The information in this email together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this email message is prohibited, unless as a necessary part of Departmental business. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network. ************************************************************************ --------------------------------------------------------------------- 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
|