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
Joe Orton wrote:
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
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
