You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/03/07 22:23:29 UTC

DO NOT REPLY [Bug 17792] New: - MaxClients directive invalid prior to ServerLimit directive

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17792>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17792

MaxClients directive invalid prior to ServerLimit directive

           Summary: MaxClients directive invalid prior to ServerLimit
                    directive
           Product: Apache httpd-2.0
           Version: 2.0.43
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: prefork
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: wrowe@apache.org


The directives;

  MaxClients         512
  ServerLimit        512

in that order results in 

  WARNING: MaxClients of 512 exceeds ServerLimit value of 256 servers,
  lowering MaxClients to 256.  To increase, please see the ServerLimit
  directive.

Reversing the directives fixes the problem.

The correct solution (so that the directives are order agnositic) is to avoid
testing MaxClients v.s. ServerLimit until the post_config phase after both
values are parsed and set.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org