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.
Bill
--- Begin Message ---
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43329
Summary: apr_proc_create behavior change
Product: APR
Version: HEAD
Platform: Other
OS/Version: Windows 2000
Status: NEW
Keywords: PatchAvailable
Severity: normal
Priority: P2
Component: APR
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
apr_proc_create now passes zero instead of INVALID_HANDLE_VALUE for STDIN,
STDOUT, and STDERR which are zero in the procattr.
This change was caused by Revision 568819.
Several 2rd-party modules (mod_fcgid, mod_fascgi, mod_perl, etc.) test
explicitly for INVALID_HANDLE_VALUE and are broken by this behavior change.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Message ---
