On Sat, 14 Jul 2001, Sander Striker wrote: > >> By having the possibility of having other children processes, you now > >> need a mechanism to kill all threads in the same process efficiently. > >> You'd need to kick them out of the accept mutex, but I'm not seeing > >> how that's going to happen quickly. -- justin > > > > You need to be able to kill all threads in a process efficiently > > regardless. We will always need to be able to re-spawn processes that > > die, and we will always have the concept of MaxRequestsPerChild. If a > > process is going to die and be replaced, then we need to kill all the > > threads in that process as quickly as possible. Only allowing one > > process at a time doesn't remove that requirement. > > The way I see it, each process has a single pool instance as the parent > for all the threads. Resetting or destroying that pool should effectively > kill all threads. What am I missing?
Nothing. Ryan _____________________________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] -----------------------------------------------------------------------------
