Paul,
this work has already been committed. apr_sigwait is a private function,
because it is completely non-portable. The solution was to remove the
apr_create_thread call from the signal thread. We now just have a
function that programs call to block on signals. They provide a signal
handling function, and it gets called. All of the threaded MPMs currently
have the main thread blocking on signals. I committed the work yesterday.
Ryan
On Fri, 13 Apr 2001, Paul J. Reder wrote:
> Ryan,
>
> In removing the extra signal thread and having the top level child_main
> block on signals, I need access to apr_sigwait from the threaded mpm.
> It currently seems to be private to APR. Am I missing something?
> If not, what is the preferred solution for APR?
>
> Thanks,
>
> --
> Paul J. Reder
> -----------------------------------------------------------
> "The strength of the Constitution lies entirely in the determination of each
> citizen to defend it. Only if every single citizen feels duty bound to do
> his share in this defense are the constitutional rights secure."
> -- Albert Einstein
>
>
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
