On Fri, Sep 07, 2007 at 02:59:10PM -0500, William Rowe wrote: > FYI - this bug appears to be the root of several modules no longer > behaving as expected on Win32 platforms. > > It takes me back to a question I raised on apr quite a while ago, > what does *unix* do with an unset child_in/child_out/child_err > procattr member? > > If it is unset, does the child inherit the processes' std handle? > AIUI - with our apr implementation, it does.
That's what the Unix implementation does; fds 0-2 will be untouched so will remain exactly as in the parent. (Of course, none of this stuff is documented as an API constraint.) joe
