You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/09/26 22:30:14 UTC

DO NOT REPLY [Bug 10515] - cgi lock when writing to stderr

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10515>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10515

cgi lock when writing to stderr





------- Additional Comments From mjc@apache.org  2002-09-26 20:30 -------
Someone asked me if this was an Apache or OS issue; I asked our kernel guys who
said:

"if nothing is reading the pipe (or the reader is held off from reading by your
writer user space locking) then 4K is the internal buffering on a linux pipe. 
You can't change that.

Ok my assessment is that you either hit a weird glibc bug in stdio with pipes or
apache 2.x has a deadlock in its own pipe handling"

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org