Jeff Trawick wrote: > > Cliff Woolley <[EMAIL PROTECTED]> writes: > > > It looks like there might be a problem with _un_graceful restarts on > > threaded, namely that the whole server just vaporizes. It doesn't do a > > clean shutdown because the pidfile is left behind, but it's gone > > nevertheless. I've yet to find evidence of a segfault happening, but that > > Unlike the child/server processes, the parent process can't rely on > the parent (itself) to write the log message for the segfault. > > Maybe sig_coredump() needs to call ap_log_error() iff called in the > parent. Something like that would clearly help. But, just to be difficult, what if ap_log_error() seg faults? We don't want recursive seg faults. Maybe some kind of "I'm trying to log a parent seg fault" footprint in sig_coredump to stop the recursion? hmmmm, I'll play with it Greg
- Re: Currently known issues wit... Jerry Baker
- Re: Currently known issues wit... Doug MacEachern
- Re: Currently known issues with 2.0.23 (very few! :... Ryan Bloom
- Re: Currently known issues with 2.0.23 Cliff Woolley
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Jeff Trawick
- Re: Currently known issues with 2.0.23 Jeff Trawick
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Jeff Trawick
- Re: Currently known issues with 2.0.23 (very few! :) Justin Erenkrantz
- Re: Currently known issues with 2.0.23 (very few! :) Ryan Bloom
- Re: Currently known issues with 2.0.23 Cliff Woolley
- Re: Currently known issues with 2.0.23 Ryan Bloom
- Re: Currently known issues with 2.0.23 Ian Holsman
- Re: Currently known issues with 2.0.23 Cliff Woolley
- Re: Currently known issues with 2.0.23 Greg Ames
- graceful restart Re: Currently known issue... Brian Pane
