*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> mkfifo (2)              
Title
Content
Arch
Section
 

MKFIFO(2)

Contents


NAME    [Toc]    [Back]

     mkfifo -- make a fifo file

LIBRARY    [Toc]    [Back]

     Standard C Library (libc, -lc)

SYNOPSIS    [Toc]    [Back]

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

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

DESCRIPTION    [Toc]    [Back]

     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.

RETURN VALUES    [Toc]    [Back]

     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.

ERRORS    [Toc]    [Back]

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

     [ENOTSUP]		The kernel has not been configured to support fifo's.

     [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]		Search permission is denied for a component of the
			path prefix.

     [ELOOP]		Too many symbolic links were encountered in translating
 the pathname.

     [EROFS]		The named file resides on a read-only file system.

     [EEXIST]		The named file exists.

     [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.

     [EIO]		An I/O error occurred while reading from or writing to
			the file system.

     [EFAULT]		The path argument points outside the process's allocated
 address space.

SEE ALSO    [Toc]    [Back]

      
      
     chmod(2), mknod(2), stat(2), umask(2)

STANDARDS    [Toc]    [Back]

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


FreeBSD 5.2.1			 June 4, 1993			 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
mkfifo IRIX make a FIFO special file
mkfifo IRIX make FIFO special file
mkfifo Linux make a FIFO special file (a named pipe)
mkfifo HP-UX make FIFO (named pipe) special files
mknod Tru64 Create a FIFO or special file
pxfisfifo IRIX Tests for pipe or a FIFO special file
mknod IRIX build special file or named pipe (FIFO)
VOP_CREATE FreeBSD create a file, socket, fifo, device, directory or symlink
VOP_SYMLINK FreeBSD create a file, socket, fifo, device, directory or symlink
VOP_MKDIR FreeBSD create a file, socket, fifo, device, directory or symlink
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service