Greg Ames <[EMAIL PROTECTED]> writes:
> 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?
AFAIK, it shouldn't be a problem. Do the ap_log_error() call after we
remove our handler ("apr_signal(sig, SIG_DFL)"), and of course ?GOVRR
from mainline as well as from the handler while testing.
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
