On Sat, Jul 14, 2001 at 01:29:35PM -0700, [EMAIL PROTECTED] wrote: > What you are missing is the history. All of the problems that we are > trying to solve were solved already in the original code. These problem > are solved most easily by using two mutexes, one for keeping only one > process in the inner loop, and the inner one for the threads in the > process. Then, when you are killing a process, you can easily wake up all > the threads in the process that are sitting on a lock. Ah. Yes, that makes more sense. But, that's not what's there now. Shall I submit a patch to threaded MPM to do this? -- justin
- RE: Terminating threads in a ... Sander Striker
- Re: Terminating threads in a ... Justin Erenkrantz
- Re: Terminiting threads in a ... Aaron Bannert
- Re: Terminiting threads in a ... rbb
- Re: Terminiting threads in a ... Aaron Bannert
- Re: Terminiting threads in a ... rbb
- Standards compliance in Apach... Justin Erenkrantz
- Re: Terminiting threads in a ... Justin Erenkrantz
- Re: Terminiting threads in a ... Aaron Bannert
- Re: Terminiting threads in a ... rbb
- Re: Terminiting threads in a ... Justin Erenkrantz
- Re: Terminiting threads in a ... rbb
- [PATCH] Add intraprocess mute... Justin Erenkrantz
- Re: Terminiting threads in a ... Aaron Bannert
- Re: Terminiting threads in a ... rbb
- Re: [PATCH] Problems with MPM threaded dean gaudet
- RE: [PATCH] Problems with MPM threaded Benjamin W. Ritcey
- Re[2]: [PATCH] Problems with MPM threa... Jeff Stuart
- Why I think we need a SPMT model was R... Justin Erenkrantz
- Re: [PATCH] Problems with MPM threaded Aaron Bannert
- Re: [PATCH] Problems with MPM threaded Justin Erenkrantz
