lkml.org 
[lkml]   [1999]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Possibly bug in Linux Kernel 2.2.1/Signal handling
Date
From
In message <36EEE92E.45ACCBCE@csi.com>, Olivier Fourdan writes:
+-----
| Linux Kernel 2.2.1 on x86 platform handles SIGPIPE signal in a strange way, at
| least different from Linux Kernel 2.0.xx, Solaris or FreeBSD. It does not emit
| the SIGPIPE signal when the pipe dies, but rather when an application tries to
| write data in it !
+--->8

I'd be rather surprised if the others didn't behave that way, since that's
how it's *supposed* to work. SIGPIPE == write on pipe with no reader.

--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
We are Linux. Resistance is an indication that you missed the point.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.066 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site