Return-Path: Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 57993 invoked by uid 500); 26 Sep 2002 20:29:28 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Apache HTTPD Bugs Notification List" Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 57982 invoked from network); 26 Sep 2002 20:29:28 -0000 Date: 26 Sep 2002 20:30:14 -0000 Message-ID: <20020926203014.10211.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 10515] - cgi lock when writing to stderr X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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