httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marion McCoskey <>
Subject [users@httpd] MaxClients stuck at 10 bug
Date Fri, 29 Apr 2011 02:11:24 GMT
This is a follow-up on my previous post, server limit stuck at 10.

I gave a whole bunch of details about what I had done trying to cope
with this problem, and got one reply saying suggesting I do what the
error message said and set the server limit.  Since I had already
tried to do that multiple times before I posted to the list, I found
that a little disappointing.  Like most men, I hate to ask directions.
 I replied to the reply with detail, but got no response.  I also
found that a little disappointing.

I had a php site using prefork.c.  Most of the php code was generate
by a couple of perl scripts.  I modified consolidated the perl scripts
into one which generates all the pages of the site in html with only a
little editing of html files required so I could switch to the
worker.c module and be thread safe.

But I was still stuck at 64 users because I got this error message:

WARNING: MaxClients (10) must be at least as large
 as ThreadsPerChild (64). Automatically
 increasing MaxClients to 64.

So I downloaded source code and looked into it some.

It seems that the worker_pre_config in worker.c is erroneously setting
max clients to 10 for some reason having to do with whether
ThreadsPerChild has been set.

Then when set_max_clients runs, MaxClients is set to 64 instead of 3
times 64 where I want it to be.  I am paying for ram and bandwith that
can't use.

Is this a configuration problem or an Apache bug?


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message