{
  "slug": "named-pipe",
  "term": "Named pipe (FIFO special file)",
  "aliases": [
    "FIFO special file",
    "FIFO special"
  ],
  "definition": "A Unix named pipe is a filesystem-named FIFO special file that connects processes through a kernel-managed byte stream rather than stored file payload.",
  "note": "mkfifo() creates the filesystem entry with access permissions determined by the requested mode and applicable creation rules. The inode type is S_IFIFO, tested with S_ISFIFO(st_mode), distinct from regular files and character devices. This record covers Unix FIFO semantics, not the Windows named-pipe API. [mkfifo-api] [inode-api] [acl-api]\n\nThe pathname locates the channel; transmitted bytes are not saved as filesystem contents. Blocking read-only or write-only open normally waits for the opposite endpoint. With O_NONBLOCK, read-only open can succeed without a writer; write-only open fails with ENXIO without a reader. Linux permits O_RDWR opening, but POSIX leaves that behavior undefined. [fifo-api]\n\nThe stream has no message boundaries. Writes of at most PIPE_BUF bytes avoid interleaving with other writers; PIPE_BUF is not the pipe capacity. For nonblocking writes within that limit, insufficient space yields EAGAIN instead of a partial write. Larger writes can interleave. These rules provide neither one read per write nor durable storage. [pipe-api] F_GETPIPE_SZ reports nominal capacity; page-buffer layout and write sizes can reduce the bytes actually writable. [pipe-capacity-api]\n\nAfter queued bytes are consumed, a positive-length read returns zero when all write-end descriptors are closed. Writing with no read-end descriptors generates SIGPIPE; if ignored, the operation fails with EPIPE. Retained duplicate endpoint descriptors therefore affect termination detection. A zero-length read is not an EOF test. [pipe-api] [read-api]",
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "related": [
    "inode",
    "regular-file"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-15",
  "citations": [
    {
      "id": "mkfifo-api",
      "title": "Linux man-pages: mkfifo(3), creation and permissions",
      "url": "https://man7.org/linux/man-pages/man3/mkfifo.3.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "inode-api",
      "title": "Linux man-pages: inode(7), FIFO file type",
      "url": "https://man7.org/linux/man-pages/man7/inode.7.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "fifo-api",
      "title": "Linux man-pages: fifo(7), pathname and open semantics",
      "url": "https://man7.org/linux/man-pages/man7/fifo.7.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "pipe-api",
      "title": "Linux man-pages: pipe(7), capacity, atomic writes and endpoint lifetime",
      "url": "https://man7.org/linux/man-pages/man7/pipe.7.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "read-api",
      "title": "Linux man-pages: read(2), zero-length requests and return values",
      "url": "https://man7.org/linux/man-pages/man2/read.2.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "acl-api",
      "title": "Linux man-pages: acl(5), object creation and default ACL inheritance",
      "url": "https://man7.org/linux/man-pages/man5/acl.5.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "pipe-capacity-api",
      "title": "Linux man-pages: F_GETPIPE_SZ(2const), nominal capacity and usable buffer space",
      "url": "https://man7.org/linux/man-pages/man2/F_GETPIPE_SZ.2const.html",
      "accessed": "2026-11-15"
    }
  ],
  "provenance": [
    "Primary-source terminology synthesis; no new IPC experiment, capacity measurement or persistence test was performed."
  ]
}
