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

CGIs do not receive sigterm





------- Additional Comments From [EMAIL PROTECTED]  2003-05-25 15:20 -------
Why do you believe you should get a SIGTERM?  Do you mean a SIGPIPE?

Your operating system should return EPIPE on a write() call where the other end 
has gone, and if you haven't masked off the signal, a SIGPIPE.  You haven't 
said what language you're using, but you should check what the default signals 
are set to.  Perhaps under FreeBSD your language X is compiled in such a way 
that SIGPIPE is ignored by default.  Try setting up a signal handler for 
SIGPIPE.

Alternatively, perhaps you are writing to a buffered stream rather than using 
write() directly, and due to buffer sizes or default buffering schemes the 
language you're using on FreeBSD is not actually trying to send the data yet.

write(2) man page:

       EPIPE  fd  is  connected to a pipe or socket whose reading
              end is closed.  When this happens the writing  pro�
              cess  will receive a SIGPIPE signal; if it catches,
              blocks or ignores this the error EPIPE is returned.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to