1 .\" Copyright (c) 1990, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)mkfifo.2 8.1 (Berkeley) 6/4/93
29 .\" $FreeBSD: src/lib/libc/sys/mkfifo.2,v 1.23 2008/04/16 13:03:12 kib Exp $
43 .Fn mkfifo "const char *path" "mode_t mode"
45 .Fn mkfifoat "int fd" "const char *path" "mode_t mode"
50 creates a new fifo file with name
52 The access permissions are
57 of the calling process.
59 The fifo's owner ID is set to the process's effective user ID.
60 The fifo's group ID is set to that of the parent directory in
65 system call is equivalent to
67 except in the case where
69 specifies a relative path.
70 In this case the newly created FIFO is created relative to the
71 directory associated with the file descriptor
73 instead of the current working directory.
76 is passed the special value
80 parameter, the current working directory is used and the behavior is
81 identical to a call to
89 will fail and no fifo will be created if:
92 The kernel has not been configured to support fifo's.
94 A component of the path prefix is not a directory.
95 .It Bq Er ENAMETOOLONG
96 A component of a pathname exceeded 255 characters,
97 or an entire path name exceeded 1023 characters.
99 A component of the path prefix does not exist.
101 A component of the path prefix denies search permission, or write permission
102 is denied on the parent directory of the fifo to be created.
104 Too many symbolic links were encountered in translating the pathname.
106 The named file would reside on a read-only file system.
108 The named file exists.
110 The parent directory of the named file has its immutable flag set, see the
112 manual page for more information.
114 The directory in which the entry for the new fifo is being placed
115 cannot be extended because there is no space left on the file
116 system containing the directory.
118 There are no free inodes on the file system on which the
119 fifo is being created.
121 The directory in which the entry for the new fifo
122 is being placed cannot be extended because the
123 user's quota of disk blocks on the file system
124 containing the directory has been exhausted.
126 The user's quota of inodes on the file system on
127 which the fifo is being created has been exhausted.
131 error occurred while making the directory entry or allocating the inode.
135 error occurred while reading from or writing to the file system.
140 points outside the process's allocated address space.
143 In addition to the errors returned by the
152 argument does not specify an absolute path and the
156 nor a valid file descriptor open for searching.
160 argument is not an absolute path and
164 nor a file descriptor associated with a directory.
175 system call is expected to conform to
179 system call follows The Open Group Extended API Set 2 specification.
183 system call appeared in