> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Trawick > Sent: 22 April 2002 16:33
> "Sander Striker" <[EMAIL PROTECTED]> writes: > > > > From: Cliff Woolley [mailto:[EMAIL PROTECTED]] > > > Sent: 18 April 2002 16:44 > > > > >> What is the current status on 2.0.36-dev? > > > Saw the fixes, so this is gone. > > > > > 2) The worker shutdown segfault ... Jeff, does the patch you committed > > > fix this for sure, or did it perhaps just hide the problem? There > > > didn't seem to be a consensus about this on-list. > > > > Jeff? > > This problem still exists. Note that I backed out a previous change I > had made which eliminated the segfaults but didn't attack the real > issue that pchild needs to live as long as our worker threads or bad > stuff will surely happen. Yes. Now the questions are: - Do we want to hold up a release for this? If so, for how long? - Is a graceless shutdown/restart at all possible with worker? [given the current APR thread API] Options I see for solving the problem are: - don't do graceless shutdown/restart, only do graceful. (not acceptable) - implement apr_thread_cancel and call this on all threads prior to cleaning pchild. - allocate the sockets out of a special pool so we can clean up the sockets (using apr_pool_clear(psock)), sleep for 1 sec (should be enough for all threads to notice the sockets are gone). After that clean pchild as usual. Sander
