Ira Childress wrote:
Did you try setting the MaxClients in the httpd.conf file:<snip>
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 150
There's no mention in the conf file about 255 being the limit, so I don't
know if setting this to 1000 is a problem or not.
I encountered this myself. If you set it to over 255 and do a graceful restart (or start it up from scratch) you get a warning about such and such number being over 255 and that apache is going to ignore what you set it at and return to 255. The message goes on to say that 255 is a hard coded limit that if you want to change, you'll have to modify the API.
--
Joseph A Nagy Jr Purgatory is where Windows users go when they
Founder and CEO die so they can figure out Linux and ascend into
Joseph A Nagy Jr Enterprises whatever higher plane one belives in.
http://jan-jr-ent.homelinux.org Linux - The Choice of Every Generation
C.S.S.: Construct Skilled in Sabotage
H.T.M.L.: Hazardous Troubleshooting and Mathematics Lifeform
http://www.brunching.com/cgi/cyborger.cgi?acronym=Linux
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
