Bug 17792 - MaxClients directive invalid prior to ServerLimit directive
Summary: MaxClients directive invalid prior to ServerLimit directive
Status: RESOLVED FIXED
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mpm_prefork (show other bugs)
Version: 2.0.43
Hardware: All All
: P3 minor (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-07 21:23 UTC by William A. Rowe Jr.
Modified: 2010-06-17 16:36 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William A. Rowe Jr. 2003-03-07 21:23:28 UTC 
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.
Comment 1 André Malo 2003-03-13 13:56:04 UTC 
a possible (and more simple ;-) solution would be EXEC_ON_READ (for
serverlimit). But this may cause side effects -- I'm not sure ;-)

The hook thing is probably better.
Comment 2 Joshua Slive 2007-06-06 06:57:45 UTC 
Please don't change the assigned-to address. We use that to capture bug traffic
in a mailing list.
Comment 3 Dan Poirier 2009-01-21 13:24:16 UTC 
This appears to be fixed in trunk.  Is it worthwhile to backport, or can this bug be closed?
Comment 4 Eric Covener 2009-01-21 14:33:30 UTC 
(In reply to comment #3)
> This appears to be fixed in trunk.  Is it worthwhile to backport, or can this
> bug be closed?
> 

out-of-order MPM settings are a big nuisance -- if there's really a fix and it's not intrusive it's probably worth considering.
Comment 5 William A. Rowe Jr. 2010-06-17 16:36:16 UTC 
Dan, as it's closed on truck, and relatively minor, I'm closing resolved.