IPB
>  Man Pages > Linux > Suse Linux 10.1 > Section 4 > fifo man page

fifo man page

Section 4 - Suse Linux 10.1 Man Pages

Other operating system man pages available here


Advanced Search

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


FIFO(4)                    Linux Programmer's Manual                   FIFO(4)




NAME

       fifo - first-in first-out special file, named pipe


DESCRIPTION

       A FIFO special file (a named pipe) is similar to a pipe, except that it
       is accessed as part of the file system.  It can be opened  by  multiple
       processes  for  reading  or writing. When processes are exchanging data
       via the FIFO, the kernel passes all data internally without writing  it
       to  the file system. Thus, the FIFO special file has no contents on the
       file system, the file system entry merely serves as a  reference  point
       so  that processes can access the pipe using a name in the file system.

       The kernel maintains exactly one pipe object for each FIFO special file
       that  is  opened  by  at least one process.  The FIFO must be opened on
       both ends (reading and writing) before data can  be  passed.  Normally,
       opening the FIFO blocks until the other end is opened also.

       A  process  can open a FIFO in non-blocking mode. In this case, opening
       for read only will succeed even if noone has opened on the  write  side
       yet;  opening  for  write  only will fail with ENXIO (no such device or
       address) unless the other end has already been opened.

       Under Linux, opening a FIFO for read and write  will  succeed  both  in
       blocking  and non-blocking mode. POSIX leaves this behaviour undefined.
       This can be used to open a FIFO for writing while there are no  readers
       available.  A process that uses both ends of the connection in order to
       communicate with itself should be very careful to avoid deadlocks.


NOTES

       When a process tries to write to a FIFO that is not opened for read  on
       the other side, the process is sent a SIGPIPE signal.

       FIFO special files can be created by mkfifo(3), and are specially indi-
       cated in ls -l.


SEE ALSO

       mkfifo(1), open(2), pipe(2),  sigaction(2),  signal(2),  socketpair(2),
       mkfifo(3), pipe(7)



Linux                             1999-06-20                           FIFO(4)


Man(1) output converted with man2html and wrapped by fishsponge

This page was generated on Tue Feb 13 02:21:48 GMT 2007

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 (5169 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 (2841 hits)
(Solaris 10 11_06)

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

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

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

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

Useful Links

Go Back

Visitor Statistics


Valid XHTML 1.0 Transitional     Valid CSS!

Partners: Cambridge Plus :: About Pyrenees Mountain Holidays :: PCB CAD Design, UK :: <Link Available>
Unix Man Pages / Linux Man Pages :: HiFi Forum :: SIP VoIP Phone & Provider Reviews :: UNIX/Linux Forum Archives

More info on advertising on Unix/Linux Forum