POSIX_MKFIFO(3) 1 POSIX_MKFIFO(3)posix_mkfifo - Create a fifo special file (a named pipe)SYNOPSIS
bool posix_mkfifo (string $pathname, int $mode)
DESCRIPTION posix_mkfifo(3) creates a special FIFO file which exists in the file system and acts as a bidirectional communication endpoint for pro-
cesses.
PARAMETERS
o $pathname
- Path to the FIFO file.
o $mode
- The second parameter $mode has to be given in octal notation (e.g. 0644). The permission of the newly created FIFO also depends
on the setting of the current umask(3). The permissions of the created file are (mode & ~umask).
RETURN VALUES
Returns TRUE on success or FALSE on failure.
NOTES
Note
When safe mode is enabled, PHP checks whether the files or directories being operated upon have the same UID (owner) as the script
that is being executed.
PHP Documentation Group POSIX_MKFIFO(3)
Check Out this Related Man Page
MKFIFO(3) Linux Programmer's Manual MKFIFO(3)NAME
mkfifo - make a FIFO special file (a named pipe)
SYNOPSIS
#include <sys/types.h>
#include <sys/stat.h>
int mkfifo(const char *pathname, mode_t mode);
DESCRIPTION
mkfifo() makes a FIFO special file with name pathname. mode specifies the FIFO's permissions. It is modified by the process's umask in
the usual way: the permissions of the created file are (mode & ~umask).
A FIFO special file is similar to a pipe, except that it is created in a different way. Instead of being an anonymous communications chan-
nel, a FIFO special file is entered into the file system by calling mkfifo().
Once you have created a FIFO special file in this way, any process can open it for reading or writing, in the same way as an ordinary file.
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 fifo(7) for nonblocking handling
of FIFO special files.
RETURN VALUE
On success mkfifo() returns 0. In the case of an error, -1 is returned (in which case, errno is set appropriately).
ERRORS
EACCES One of the directories in pathname did not allow search (execute) permission.
EEXIST pathname already exists. This includes the case where pathname is a symbolic link, dangling or not.
ENAMETOOLONG
Either the total length of pathname is greater than PATH_MAX, or an individual filename component has a length greater than
NAME_MAX. In the GNU system, there is no imposed limit on overall filename length, but some file systems may place limits on the
length of a component.
ENOENT A directory component in pathname does not exist or is a dangling symbolic link.
ENOSPC The directory or file system has no room for the new file.
ENOTDIR
A component used as a directory in pathname is not, in fact, a directory.
EROFS pathname refers to a read-only file system.
CONFORMING TO
POSIX.1-2001.
SEE ALSO mkfifo(1), close(2), open(2), read(2), stat(2), umask(2), write(2), mkfifoat(3), fifo(7)COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
GNU 2008-06-12 MKFIFO(3)