[EMAIL PROTECTED] writes:
> ThreadsPerChild should NOT include the signal thread. That directive
> talks about how many worker threads you have, not total threads.
Okay, I'm glad we're on the same page!
What is the explanation for the " - 1" in the next expression which
controls how many threads we create in the new child?
for (i=0; i < ap_threads_per_child - 1; i++) {
It was added when you started creating the signal thread, so I assumed
that your reasoning was that ThreadsPerChild includes worker threads +
signal threads.
Besides not starting enough worker threads per child, the scoreboard
maintenance is also confused because the SERVER_DEAD entry
(uninitialized) in the slot for thread ap_threads_per_child-1 keeps it
from counting the threads of that child in the number of idle threads.
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
