www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Curtis <ccur...@aet-usa.com>
Subject os-solaris/3467: Broken client connections not detected
Date Tue, 01 Dec 1998 03:55:09 GMT

>Number:         3467
>Category:       os-solaris
>Synopsis:       Broken client connections not detected
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Nov 30 21:10:00 PST 1998
>Originator:     ccurtis@aet-usa.com
>Release:        1.3.3
SunOS yacht 5.4 Generic_101945-44 sun4m sparc
GCC 2.7.2.f.1
mod_php 3.0.5
I have a PHP page that sits in an infinite loop.  When a browser leaves this page, the child
httpd recieves a SIGPIPE, but ignores it, and continues to run, even though the client is
long gone.  The output of a truss:

read(7, "05 C h r i s\t 9 1 2 4 8".., 52)       = 52
read(7, "01\0\0\n", 4)                          = 4
read(7, "FE", 1)                                = 1
write(6, " < f o n t   c o l o r =".., 182)     Err#32 EPIPE
    Received signal #13, SIGPIPE [ignored]
The URL is
but please dont.
I haven't looked at the source code, but it seems like a good idea not to ignore SIGPIPE.
 There may be other reasons to ignore it that I'm not aware of, however.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message