From: "Ryan Bloom" <[EMAIL PROTECTED]>
Sent: Thursday, July 19, 2001 1:00 PM
> Yep. The inherit flag only affects apr_create_process. Since we
> create child processes with fork, the inherit flag has no affect.
> Basically, the inherit flag will not be able to affect fork() until
> fork() becomes a real part of APR, which means somebody needs to
> implement it on Windows. :-)
apr_status_t apr_fork(...)
{
return APR_ENOTIMPL;
}
:-)
> > Again, let's compare the current cvs tree (including the threaded
> > mpm) to our one and only 2.0 beta. I believe the current code wins
> > hands down, or am I missing something?
>
> Not in my mind. +1 for a tag and roll.
+1
- daedalus is back on 2.0.21-dev Greg Ames
- Re: daedalus is back on 2.0.21-dev Greg Ames
- Re: daedalus is back on 2.0.21-dev Cliff Woolley
- Tag 2.0.21 was Re: daedalus is back on 2.0.2... Justin Erenkrantz
- Re: Tag 2.0.21 was Re: daedalus is back ... Greg Ames
- Re: Tag 2.0.21 was Re: daedalus is b... Ryan Bloom
- Re: Tag 2.0.21 was Re: daedalus... William A. Rowe, Jr.
- Re: Tag 2.0.21 was Re: daed... Ryan Bloom
- Re: Tag 2.0.21 was Re: daedalus is b... Justin Erenkrantz
- Re: Tag 2.0.21 was Re: daedalus... Greg Ames
- Re: Tag 2.0.21 was Re: daed... Justin Erenkrantz
- Re: Tag 2.0.21 was Re: daedalus... William A. Rowe, Jr.
- Re: Tag 2.0.21 was Re: daed... Justin Erenkrantz
- Pool allocation bottlenecks... Brian Pane
- Re: Tag 2.0.21 was Re: daed... William A. Rowe, Jr.
- RE: daedalus is back on 2.0.21-dev Gonyou, Austin
- Re: daedalus is back on 2.0.21-dev Justin Erenkrantz
