MKFIFO(2)

🎀 MKFIFO(2) — mkfifo, mkfifoat: make a fifo file 🎀

okay bestie, welcome to the MKFIFO(2) page from the System Calls Manual. We're folding the manual name in right at the top instead of copying the header line, because we're iconic like that. 💅

🌸 NAME 🌸

mkfifo, mkfifoat — make a fifo file.

📚 LIBRARY 📚

Standard C Library (libc, -lc). She's the one holding it down.

✨ SYNOPSIS ✨

#include <sys/types.h>
#include <sys/stat.h>

int
mkfifo(const char *path, mode_t mode);

int
mkfifoat(int fd, const char *path, mode_t mode);

💖 DESCRIPTION 💖

The mkfifo() system call creates a new fifo file with name path. The access permissions are specified by mode and restricted by the umask(2) of the calling process.

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.

The mkfifoat() 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 special value AT_FDCWD in the fd parameter, the current working directory is used and the behavior is identical to a call to mkfifo().

🫶 RETURN VALUES 🫶

The mkfifo() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. slay.

😭 ERRORS 😭

The mkfifo() system call will fail and no fifo will be created if:

• ENOTSUP — the kernel has not been configured to support fifo's. oof.
• ENOTDIR — a component of the path prefix is not a directory.
• ENAMETOOLONG — a component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
• ENOENT — a component of the path prefix does not exist.
• EACCES — a component of the path prefix denies search permission, or write permission is denied on the parent directory of the fifo to be created.
• ELOOP — too many symbolic links were encountered in translating the pathname.
• EROFS — the named file would reside on a read-only file system.
• EEXIST — the named file exists.
• EPERM — the parent directory of the named file has its immutable flag set, see the chflags(2) manual page for more information.
• ENOSPC — 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.
• ENOSPC — there are no free inodes on the file system on which the fifo is being created.
• EDQUOT — 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.
• EDQUOT — the user's quota of inodes on the file system on which the fifo is being created has been exhausted.
• EIO — an I/O error occurred while making the directory entry or allocating the inode.
• EINTEGRITY — corrupted data was detected while reading from the file system.
• EFAULT — the path argument points outside the process's allocated address space.

In addition to the errors returned by the mkfifo(), the mkfifoat() may fail if:

• EBADF — the path argument does not specify an absolute path and the fd argument is neither AT_FDCWD nor a valid file descriptor open for searching.
• ENOTDIR — the path argument is not an absolute path and fd is neither AT_FDCWD nor a file descriptor associated with a directory.

🔥 SEE ALSO 🔥

chflags(2), chmod(2), mknod(2), stat(2), umask(2) — go read these too, bestie. iykyk.

⭐ STANDARDS ⭐

The mkfifo() system call is expected to conform to ISO/IEC 9945-1:1990 (“POSIX.1”).

The mkfifoat() system call follows The Open Group Extended API Set 2 specification.

🦋 HISTORY 🦋

The mkfifoat() system call appeared in FreeBSD 8.0.

---

mwah 💋 — this page is from Debian, dated March 30, 2020, and the manual name is MKFIFO(2).