hi all… recently upgraded to 2.4.12. i know that the server creates this awesome "dummy" processes when it needed to be ready and handle requests. that's all good and well.question is: shouldn't those die when there hasn't been much happening for a while and keeping a lot of them "just in case" is not needed that badly?the lines at the bottom of this message are form the server-status output. the number of those lines eventually grows but it never goes down. which is weird, right? … i know….also how come the number of those extra processes doesn't match the one fromps -auwx | grep httpd?my guess is that the "dummy" connections (since they don't have their own process attached to them) are there because some of the other processes that do show in ps ask for those at various stages. is it true? how would i know which one asked? does it matter?i've experienced some issues where the (open?!) "dummy" connections become so many that the server stops responding but the ps -auwx | grep httpd shows just 10 processes or so running. after restart everything goes back to normal. except i'm not always there to restart…so one though i had about this is that in my httpd-mpm file the only loaded module is mpm_prefork_module. which has this in it's scope (default values):StartServers 5MinSpareServers 5MaxSpareServers 10MaxRequestWorkers 250MaxConnectionsPerChild 0is it reasonable to believe that MaxConnectionsPerChild should have some reasonable limit? will this control how many "dummy" connections are kept alive?thanks…
|