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

  man pages->OpenBSD man pages -> pipe (2)              



NAME    [Toc]    [Back]

     pipe - create descriptor pair for interprocess communication

SYNOPSIS    [Toc]    [Back]

     #include <unistd.h>

     pipe(int fildes[2]);

DESCRIPTION    [Toc]    [Back]

     The  pipe()  function creates a pipe, which is an object allowing unidirectional
 data flow, and allocates a pair of file  descriptors.
The first
     descriptor  connects  to  the  read end of the pipe, and the
second connects
     to the write end, so that data written to fildes[1]  appears
on (i.e., can
     be read from) fildes[0].  This allows the output of one program to be
     sent to another program: the source's standard output is set
up to be the
     write  end of the pipe, and the sink's standard input is set
up to be the
     read end of the pipe.  The pipe itself  persists  until  all
its associated
     descriptors are closed.

     A pipe whose read or write end has been closed is considered
     Writing on such a pipe causes the writing process to receive
     signal.   Widowing a pipe is the only way to deliver end-offile to a
     reader: after the reader consumes any buffered data, reading
a widowed
     pipe returns a zero count.

RETURN VALUES    [Toc]    [Back]

     On  successful creation of the pipe, zero is returned.  Otherwise, a value
     of -1 is returned and the variable errno set to indicate the

ERRORS    [Toc]    [Back]

     The pipe() call will fail if:

     [EMFILE]      Too many descriptors are active.

     [ENFILE]      The system file table is full.

     [EFAULT]      The fildes buffer is in an invalid area of the
                   address space.

SEE ALSO    [Toc]    [Back]

     sh(1), fork(2), read(2), socketpair(2), write(2)

STANDARDS    [Toc]    [Back]

     The  pipe()  function  conforms  to  IEEE  Std   1003.1-1988

     As  an  extension,  the pipe provided is actually capable of
moving data
     bidirectionally.  This is compatible  with  SVR4.   However,
this is nonPOSIX
  behaviour  which should not be relied on, for reasons
of portability.

HISTORY    [Toc]    [Back]

     A pipe() function call appeared in Version 3 AT&T UNIX.

OpenBSD      3.6                           June      4,      1993
[ Back ]
 Similar pages
Name OS Title
socket Tru64 Create an end point for communication and return a descriptor
ftok Tru64 Generate a standard interprocess communication key
ipc Linux System V interprocess communication mechanisms
stdipc IRIX standard interprocess communication package
unix Linux Sockets for local interprocess communication.
ipcs HP-UX report status of interprocess communication facilities
ipcs Tru64 Reports Interprocess Communication (IPC) facility status
ipcs OpenBSD report System V interprocess communication facilities status
pipcs HP-UX report status of POSIX interprocess communication facilities
ipcs FreeBSD report System V interprocess communication facilities status
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service