jim 99/04/20 14:40:59
Modified: conf highperformance.conf-dist httpd.conf-dist Log: Change of the conf-dist default setting for MaxRequestsPerChild, as well as some notes about it Revision Changes Path 1.3 +2 -1 apache-1.3/conf/highperformance.conf-dist Index: highperformance.conf-dist =================================================================== RCS file: /export/home/cvs/apache-1.3/conf/highperformance.conf-dist,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- highperformance.conf-dist 1998/10/03 11:05:05 1.2 +++ highperformance.conf-dist 1999/04/20 21:40:58 1.3 @@ -18,7 +18,8 @@ StartServers 5 MinSpareServers 5 MaxSpareServers 10 -MaxRequestsPerChild 10000000 +# Assume no memory leaks at all +MaxRequestsPerChild 0 # this is a True Config File # see http://www.apache.org/info/three-config-files.html 1.41 +8 -2 apache-1.3/conf/httpd.conf-dist Index: httpd.conf-dist =================================================================== RCS file: /export/home/cvs/apache-1.3/conf/httpd.conf-dist,v retrieving revision 1.40 retrieving revision 1.41 diff -u -r1.40 -r1.41 --- httpd.conf-dist 1999/04/20 18:03:09 1.40 +++ httpd.conf-dist 1999/04/20 21:40:59 1.41 @@ -158,9 +158,15 @@ # as to avoid problems after prolonged use when Apache (and maybe the # libraries it uses) leak memory or other resources. On most systems, this # isn't really needed, but a few (such as Solaris) do have notable leaks -# in the libraries. +# in the libraries. For these platforms, set to something like 10000 +# or so; a setting of 0 means unlimited. # -MaxRequestsPerChild 30 +# NOTE: This value does not include keepalive requests after the initial +# request per connection. For example, if a child process handles +# an initial request and 10 subsequent "keptalive" requests, it +# would only count as 1 request towards this limit. +# +MaxRequestsPerChild 0 # # Listen: Allows you to bind Apache to specific IP addresses and/or
