httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14299] - SIGPIPE problem
Date Wed, 06 Nov 2002 17:46:29 GMT
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=14299>.
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=14299

SIGPIPE problem

trawick@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From trawick@apache.org  2002-11-06 17:46 -------
Here is what happens with SIGPIPE and Apache:

The kernel raises SIGPIPE when Apache tries to write to a dropped 
connection, the signal is ignored (because Apache chose to ignore
the signal), then Apache sees -1/errno from writev() and does the
right thing.  What you show in gdb is perfectly normal.  If you 
continue from the point that gdb sees the SIGPIPE, you should
see Apache react to a failure from writev() and clean up the
connection.

You may have some 3rd party code which changes the way SIGPIPE is
handled for Apache child processes.  That isn't something we can
debug.  Possibly your PHP extension is mucking with the required SIGPIPE 
handling.  Look into what PHP does, what your extension does, and what any 
libraries used by either of those do with SIGPIPE.

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


Mime
View raw message