aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-03-11 07:55:20 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-03-11 07:58:17 +0100
commit98faa645eaa241ce726d1bc4556b440a448f6610 (patch)
tree387278655512478950e46fd6d32ef0539bda98a1
parent7255c7c0dfbbacdbca03a53f1cd4563e781627af (diff)
downloadman-pages-98faa645eaa241ce726d1bc4556b440a448f6610.tar.gz
pipe.7: Clarify that I/O signalling requires use of both F_SETOWN and O_ASYNC
Reported-by: Jason Vas Dias <jason.vas.dias@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man7/pipe.77
1 files changed, 4 insertions, 3 deletions
diff --git a/man7/pipe.7 b/man7/pipe.7
index 0dfc798039..f90666da16 100644
--- a/man7/pipe.7
+++ b/man7/pipe.7
@@ -227,10 +227,11 @@ Setting the
.B O_ASYNC
flag for the read end of a pipe causes a signal
.RB ( SIGIO
-by default) to be generated when new input becomes available on the pipe
-(see
+by default) to be generated when new input becomes available on the pipe.
+The target for delivery of signals must be set using the
.BR fcntl (2)
-for details).
+.B F_SETOWN
+command.
On Linux,
.B O_ASYNC
is supported for pipes and FIFOs only since kernel 2.6.