From 98faa645eaa241ce726d1bc4556b440a448f6610 Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Fri, 11 Mar 2016 07:55:20 +0100
Subject: [PATCH] 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>
---
 man7/pipe.7 | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/man7/pipe.7 b/man7/pipe.7
index 0dfc79803..f90666da1 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.