DO NOT REPLY [Bug 36428] New: - ref. 28816 - mod_cgi still doesn't work right re: closing stderr

[bu...@apache.org]

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=36428>.
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=36428

           Summary: ref. 28816 - mod_cgi still doesn't work right re:
                    closing stderr
           Product: Apache httpd-2.0
           Version: 2.0.54
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_cgi
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: rmiller@duskglow.com


I am opening a new bug here because 28816 was already marked as a dup and I was 
pointed to the patch that was supposed to fix the stderr > 4096 bytes problem.  
I applied that patch to 2.0.54 (I thought it was already committed??), however, 
it did not fix the problem that I am having. 
 
I still cannot detach a script without closing stderr.  1.3 worked just fine - 
all I had to do was dup stderr, close it, then reassign the dup()ed fd back to 
stderr.  This does not work on 2.0.54.  I need to be able to somehow signal 
apache to go about its business while still keeping stderr open and writable. 
 
What do you need for a test case?

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org