Lines Matching full:pipe

347 pipe
350 one process writes into the pipe,
366 the pipe connection is established and used.
369 .UL pipe
370 creates a pipe.
371 Since a pipe is used for both reading and writing,
377 stat = pipe(fd);
384 is the read side of the pipe and
394 If a process reads a pipe which is empty,
396 if a process writes into a pipe which
397 is too full, it will wait until the pipe empties somewhat.
398 If the write side of the pipe is closed,
428 through the pipe.
432 the pipe with a
433 .UL pipe
439 closes the other side of the pipe,
443 The parent likewise closes the end of the pipe it does not use.
446 fails to close the write end of the pipe, it will never
447 see the end of the pipe file, just because there is one writer
463 	if (pipe(p) < 0)
487 closes the write side of the pipe,
494 are the conventional way to associate the pipe descriptor
508 is to copy the file descriptor for the pipe (read side)
510 thus the read side of the pipe becomes the standard input.
512 Finally, the old read side of the pipe is closed.
522 to close the pipe created by
540 pclose(fd)	/* close pipe fd */
566 The routine as written has the limitation that only one pipe may