mkfifo man page

Section 3 - Suse Linux 10.1 Man Pages

Other operating system man pages available here

Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!

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 channel,
       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(4) for non-blocking 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 (exe-
              cute) permission.

       EEXIST pathname already exists.

       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 over-
              all  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  dan-
              gling symbolic link.

       ENOSPC The directory or filesystem 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 filesystem.

CONFORMING TO

       POSIX.1

SEE ALSO

       mkfifo(1), close(2), open(2),  read(2),  stat(2),  umask(2),  write(2),
       mkfifoat(3), fifo(4)



Linux 1.2.13                      1995-09-03                         MKFIFO(3)

Your favourite pages:

No pages logged yet.
Trying to save cookie...

Top 10 most popular pages:

sqlite3 man page (5323 hits)
(openSUSE 10.2)

svn man page (5176 hits)
(FreeBSD 6.2)

adv_cap_autoneg man page (4865 hits)
(Solaris 10 11_06)

CPAN man page (4602 hits)
(Suse Linux 10.1)

ssh man page (4337 hits)
(Suse Linux 10.1)

ssh-socks5-proxy-connect man page (2843 hits)
(Solaris 10 11_06)

netcat man page (2690 hits)
(Suse Linux 10.1)

pprosetup man page (2474 hits)
(Solaris 10 11_06)

startproc man page (2456 hits)
(Suse Linux 10.1)

signal man page (2395 hits)
(Suse Linux 10.1)