pipe(2) [hpux man page]

pipe(2) 							System Calls Manual							   pipe(2)

NAME

       pipe() - create an interprocess channel

SYNOPSIS

DESCRIPTION

       creates	an  I/O  mechanism  called  a pipe and returns two file descriptors, fildes[0] and fildes[1].  fildes[0] is opened for reading and
       fildes[1] is opened for writing.

       A read-only file descriptor fildes[0] accesses the data written to fildes[1] on a first-in-first-out (FIFO) basis.  For details of the  I/O
       behavior of pipes see read(2) and write(2).

       By  default,  HP-UX  pipes are not STREAMS-based.  It is possible to generate the kernel so that all pipes created on a system are STREAMS-
       based.  This can only be done for HP-UX releases 10.0 and later.  STREAMS-based FIFOs (created by or are not supported on HP-UX.

       To generate a kernel that supports STREAMS-based pipes:

	 o  STREAMS/UX must be installed.

	 o  The module and the driver must be included in the file.  (When STREAMS/UX is installed, and are  automatically  added  to  the  system
	    file.)

	 o  The  tunable  parameter  (see  streampipes(5))  must  be  set  to  1  in the file.	(This is not automatically done when STREAMS/UX is
	    installed.)

	 o  The kernel must be generated and the system rebooted.  Once this is done, all pipes created by will be STREAMS-based.

       For more information, see

EXAMPLES

       The following example uses to implement the command string

RETURN VALUE

       returns one of the following values:

	      Successful completion.

	      Failure.
		     is set to indicate the error.

ERRORS

       sets to one of the following error values if the corresponding condition is true.

       or more file descriptors are currently open.

       The system file table is full.

       The file system lacks sufficient space to create the pipe.

       Could not allocate resources for both Stream heads
		      (STREAMS-based pipes only).

SEE ALSO

       sh(1), read(2), write(2), popen(3S), privileges(5), streampipes(5), streamio(7).

STANDARDS CONFORMANCE

																	   pipe(2)

PIPE(2) 						      BSD System Calls Manual							   PIPE(2)

NAME

     pipe, pipe2 -- create descriptor pair for interprocess communication

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <unistd.h>

     int
     pipe(int fildes[2]);

     int
     pipe2(int fildes[2], int flags);

DESCRIPTION

     The pipe() system call creates a pipe, which is an object allowing bidirectional data flow, and allocates a pair of file descriptors.

     The pipe2() system call allows control over the attributes of the file descriptors via the flags argument.  Values for flags are constructed
     by a bitwise-inclusive OR of flags from the following list, defined in <fcntl.h>:

     O_CLOEXEC	 Set the close-on-exec flag for the new file descriptors.

     O_NONBLOCK  Set the non-blocking flag for the ends of the pipe.

     If the flags argument is 0, the behavior is identical to a call to pipe().

     By convention, the first descriptor is normally used as the read end of the pipe, and the second is normally 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 that has had an end closed is considered widowed.  Writing on such a pipe causes the writing process to receive a SIGPIPE signal.
     Widowing a pipe is the only way to deliver end-of-file to a reader: after the reader consumes any buffered data, reading a widowed pipe
     returns a zero count.

     The bidirectional nature of this implementation of pipes is not portable to older systems, so it is recommended to use the convention for
     using the endpoints in the traditional manner when using a pipe in one direction.

RETURN VALUES

     The pipe() 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

     The pipe() and pipe2() system calls will fail if:

     [EMFILE]		Too many descriptors are active.

     [ENFILE]		The system file table is full.

     [ENOMEM]		Not enough kernel memory to establish a pipe.

     The pipe2() system call will also fail if:

     [EINVAL]		The flags argument is invalid.

SEE ALSO

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

HISTORY

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

     Bidirectional pipes were first used on AT&T System V Release 4 UNIX.

     The pipe2() function appeared in FreeBSD 10.0.

BSD
								    May 1, 2013 							       BSD