From af5b2ef2cc3c20d6245ccb99a95abdc225181150 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Fri, 21 Apr 2006 01:46:04 +0000 Subject: [PATCH] fifo.4 --> fifo.7 --- man2/open.2 | 4 ++-- man3/mkfifo.3 | 4 ++-- man7/pipe.7 | 6 +++--- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/man2/open.2 b/man2/open.2 index 26785a90c..bb88a07ff 100644 --- a/man2/open.2 +++ b/man2/open.2 @@ -245,7 +245,7 @@ When possible, the file is opened in non-blocking mode. Neither the nor any subsequent operations on the file descriptor which is returned will cause the calling process to wait. For the handling of FIFOs (named pipes), see also -.BR fifo (4). +.BR fifo (7). For a discussion of the effect of .BR O_NONBLOCK in conjunction with mandatory file locks and with file leases, see @@ -556,4 +556,4 @@ corresponding to the flags \fBO_SYNC\fR, \fBO_DSYNC\fR and .BR unlink (2), .BR write (2), .BR fopen (3), -.BR fifo (4) +.BR fifo (7) diff --git a/man3/mkfifo.3 b/man3/mkfifo.3 index 3f868249d..68c8c3b9d 100644 --- a/man3/mkfifo.3 +++ b/man3/mkfifo.3 @@ -51,7 +51,7 @@ However, it has to be open at both ends simultaneously before you can proceed to do any input or output operations on it. Opening a FIFO for reading normally blocks until some other process opens the same FIFO for writing, and vice versa. See -.BR fifo (4) +.BR fifo (7) for non-blocking handling of FIFO special files. .SH "RETURN VALUE" On success \fImkfifo\fP() returns 0. In @@ -97,4 +97,4 @@ POSIX.1 .BR umask (2), .BR write (2), .BR mkfifoat (3), -.BR fifo (4) +.BR fifo (7) diff --git a/man7/pipe.7 b/man7/pipe.7 index e393c0844..b17be3e44 100644 --- a/man7/pipe.7 +++ b/man7/pipe.7 @@ -54,7 +54,7 @@ flag; the write end is opened using the .B O_WRONLY flag. See -.BR fifo (4) +.BR fifo (7) for further details. .IR Note : although FIFOs have a pathname in the file system, @@ -235,5 +235,5 @@ bidirectional pipe semantics. .BR socketpair (2), .BR stat (2), .BR mkfifo (3), -.BR fifo (4), -.BR epoll (7) +.BR epoll (7), +.BR fifo (7)