summaryrefslogtreecommitdiff
path: root/manual/signal.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1992-09-25 06:51:20 +0000
committerRichard M. Stallman <rms@gnu.org>1992-09-25 06:51:20 +0000
commit02be1810a23a9e95536aceec2ed16dccf471d1e4 (patch)
tree8546ffef39ceb3607b80bfd6436e4a846eeb70b0 /manual/signal.texi
parentca3208904fe03d877d24be042047322c95b76368 (diff)
For SIGPIPE, mention use with sockets.
Diffstat (limited to 'manual/signal.texi')
-rw-r--r--manual/signal.texi13
1 files changed, 8 insertions, 5 deletions
diff --git a/manual/signal.texi b/manual/signal.texi
index 23cf5570a1..0df13e9903 100644
--- a/manual/signal.texi
+++ b/manual/signal.texi
@@ -641,14 +641,17 @@ action for all of them is to cause the process to terminate.
@comment signal.h
@comment POSIX.1
@deftypevr Macro int SIGPIPE
-If you use pipes or FIFO special files, you have to design your
-application so that one process opens the pipe for reading before
-another starts writing. If the reading process never starts, or
-terminates unexpectedly, a write to the pipe or FIFO causes the writing
-process to receive a @code{SIGPIPE} signal.
+If you use pipes or FIFOs, you have to design your application so that
+one process opens the pipe for reading before another starts writing.
+If the reading process never starts, or terminates unexpectedly, a write
+to the pipe or FIFO causes the writing process to receive a
+@code{SIGPIPE} signal.
Pipes and FIFO special files are discussed in more detail in @ref{Pipes
and FIFOs}.
+
+@code{SIGPIPE} also occurs when you try to output to a socket that isn't
+connected. @xref{Sending Data}.
@end deftypevr
@cindex pipe signal
@cindex broken pipe signal