httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: server reached MaxClients setting
Date Thu, 20 Sep 2001 15:34:13 GMT
Sascha Schumann wrote:
> 
> On Thu, 20 Sep 2001, Jim Jagielski wrote:
> 
> > At 11:33 AM -0300 9/20/01, Daniel Abad wrote:
> > >Is it really a problem??? Or just warning?
> > >
> > >[Thu Sep 20 00:28:53 2001] [error] server reached MaxClients setting,
> > >consider raising the MaxClients setting
> > >
> >
> > No doubt, you are getting hammered by Nimba causing your server to
> > spawn extra processes to handle the increased load... So actually,
> > it's a *good* thing since it's preventing the attack from
> > consuming all your server resources.
> 
>     Or he is serving large files to slow clients, so that a lot
>     of Apache processes are blocked for a longer period of time.
>     That happens regularly to www.php.net with MaxClients 256.
>     One way to fix that is recompiling Apache to handle even more
>     clients, but that increases the overall RAM usage of course.
>     So we usually just choose the lazy route, install an
>     additional thttpd and redirect requests as appropiate.
> 

Hell it could be a ton of things (someone uploaded a nude picture
of Bridget Fonda on his server)... 

-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
      "A society that will trade a little liberty for a little order
                   will lose both and deserve neither"

Mime
View raw message