Re: [Slashcode-general] Long runing httpd processes from Slashcode

[George C. <ga...@sp...>]

** Reply to message from "Blake Carver" <li...@li...> on Fri, 26
Sep 2003 22:47:19 -0400

Hi Blake,

> Has anyone else had problems with Slashcode spawing evil httpd processes
> that won't die, and eventually start to take up all memory and/or processor
> power? Should there be any httpd processes that run on forever from
> slashcode?

I don't believe that Slash spawns any httpd processes.  The background
slashd task can fire off a number of perl processes, but not httpd.

Apache will start and leave servers running to manage its workload.  What
do you have in your httpd.conf file for the server pool management.  My
server is not very busy at all, here are my settings.

MinSpareServers 3
MaxSpareServers 7
StartServers 3
MaxClients 30
MaxRequestsPerChild 50

So with the above, apache will initially start 3 httpd servers, try to
keep 3 spare servers running, no more than 7, and can have as many as 30
servers. When a server has processes 50 requests it will be killed and
restarted.

George