apachectl start loads 11 apache's into memory ?

 > If you want less of them, change the configuration of Apache to spawn
 > less child process.

Do you mean I need to eliminate some of these setting I used when I
compiled apache 2.0.53 ?
--enable-so \
--enable-cgi \
--enable-info \
--enable-rewrite \
--enable-speling \
--enable-usertrack \
--enable-deflate \
--enable-ssl \
--enable-mime-magic

My apache is supporting a web site that uses the PHP engine. Eventually
MYSQL.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: apachectl start loads 11 apache's into memory ? 

 > If you want less of them, change the configuration of Apache to spawn
 > less child process.

Or does it mean just editing my httpd.conf
Actually apache is supporting two virtual domains. Would this account
for all the threads?

thank you
craig<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: apachectl start loads 11 apache's into memory ? 

craig wrote:
 >
 >
  >> If you want less of them, change the configuration of Apache to spawn
  >> less child process.
 >
 >
 > Or does it mean just editing my httpd.conf
 > Actually apache is supporting two virtual domains. Would this account
 > for all the threads?
 >

I'm assuming you're running Unix/Linux (based on the output of ps), so
it looks like you're using the prefork MPM. This means that to alter the
number of (idle) child processes you have, you'll want to play with the
MinSpareServers directive to control how many waiting processes you
have. However, keep in mind that Apache is dependant on these waiting
processes to be able to process multiple request concurrently.

Gabriel<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: apachectl start loads 11 apache's into memory ? 

this post is not archived.
 >> Stay informed about: apachectl start loads 11 apache's into memory ? 

However, keep in mind that Apache is dependant on these waiting
 > processes to be able to process multiple request concurrent


To my supporters

I'm dealing with a very peculiar situation. I saw all those child apache
process and thought maybe this might have something to do with it.

I'm running a php blog on both of my domains. One happend to be password
protected, oh and the other thing is that I outsourced the DNS providers
.. Each domain is using a different DNS provider.

I just changed out the router. Again I'm trying to eliminate a problem
I've yet to define. Now however I guess I've gotten deaper into a hole,
nother neither sites are accessable.

The problem was/is that on one of the sites the "public one" it required
not only the alias www but to qualify the URL with /idex.php to pull up
the site from my system. Other's, that is those from the WAN side were
not having any of these difficulties. I thought maybe my router was
somehow unable to resolve the URL, so I switched it out. At the same
time I created this thread to try and glean some explaination on what or
why apache ran "all" these child processes. I guess in short it needs
them, but I'm not really any clearer why.

thanks<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: apachectl start loads 11 apache's into memory ?