|MKFIFO(2)||System Calls Manual||MKFIFO(2)|
— make a fifo file
Standard C Library (libc, -lc)
char *path, mode_t
fd, const char
The fifo's owner ID is set to the process's effective user ID. The fifo's group ID is set to that of the parent directory in which it is created.
system call is equivalent to
mkfifo() except in the
case where path specifies a relative path. In this
case the newly created FIFO is created relative to the directory associated
with the file descriptor fd instead of the current
working directory. If
mkfifoat() is passed the
AT_FDCWD in the
fd parameter, the current working directory is used
and the behavior is identical to a call to
mkfifo() function returns the
value 0 if successful; otherwise the value -1 is returned and
the global variable errno is set to indicate the
mkfifo() system call will fail and no
fifo will be created if:
- The kernel has not been configured to support fifo's.
- A component of the path prefix is not a directory.
- A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
- A component of the path prefix does not exist.
- A component of the path prefix denies search permission, or write permission is denied on the parent directory of the fifo to be created.
- Too many symbolic links were encountered in translating the pathname.
- The named file would reside on a read-only file system.
- The named file exists.
- The parent directory of the named file has its immutable flag set, see the chflags(2) manual page for more information.
- The directory in which the entry for the new fifo is being placed cannot be extended because there is no space left on the file system containing the directory.
- There are no free inodes on the file system on which the fifo is being created.
- The directory in which the entry for the new fifo is being placed cannot be extended because the user's quota of disk blocks on the file system containing the directory has been exhausted.
- The user's quota of inodes on the file system on which the fifo is being created has been exhausted.
- An I/O error occurred while making the directory entry or allocating the inode.
- Corrupted data was detected while reading from the file system.
- The path argument points outside the process's allocated address space.
In addition to the errors returned by the
mkfifo() system call is expected to
conform to IEEE Std 1003.1-1990
system call follows The Open Group Extended API Set 2 specification.
mkfifoat() system call appeared in
|March 30, 2020||Debian|