Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
MKFIFO(2) OpenBSD Programmer's Manual MKFIFO(2)
NAME
mkfifo - make a fifo file
SYNOPSIS
#include <sys/types.h>
#include <sys/stat.h>
int
mkfifo(const char *path, mode_t mode);
DESCRIPTION
mkfifo() creates a new fifo file with name path. The access permissions
are specified by mode and restricted by the umask(2) of the calling pro-
cess.
The fifo's owner ID is set to the process's effective user ID. The fi-
fo's group ID is set to that of the parent directory in which it is cre-
ated.
RETURN VALUES
A 0 return value indicates success. A -1 return value indicates an er-
ror, and an error code is stored in errno.
ERRORS
mkfifo() will fail and no fifo will be created if:
[EOPNOTSUPP] 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 {NAME_MAX} characters,
or an entire path name exceeded {PATH_MAX} 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] path points outside the process's allocated address space.
SEE ALSO
chmod(2), stat(2), umask(2)
STANDARDS
The mkfifo function call conforms to IEEE Std1003.1-1988 (``POSIX'').
OpenBSD 2.6 June 4, 1993 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
Up to: Local Process Communication - Communication between processes running on the same system. Synchronization. File locking. Signals. FIFOs, pipes, et al
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware > man pages >
mkfifo.2/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|