03-01-2011
Methyl, is a pipe not considered standard input?
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
Im new to all this but the computer club im in has unix i think.
now my questions.
1.is it NTFS i need to partion the harddrive with to be able to use unix?
2.Unix and Linux whats the diffrense?yes im a noob got no idea been using crap windows for ages and hate it.
3.I got a win98... (2 Replies)
Discussion started by: Pierre
2 Replies
2. Programming
What does "extern" do?
ex. extern int x;
and another question, what about using static in functions? like: static void foo(), why? (2 Replies)
Discussion started by: Esaia
2 Replies
3. Solaris
Hello Everbody
I hope you can give me a hand, I have some questions
The first one itīs about some message that I donīt know what means, I was looking about it. but nothing. This is the message
rsh: connection from bad port
bsd-gw: Error reading from connection: Bad file number
And my... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
4. UNIX for Dummies Questions & Answers
Hi everyone im new to this forums, i just wanted to get started by asking a few question(Im a Unix newbie)
1. How do i sort a file called "dirr" in a ascending order on the 3rd column
2. what does alias on=who do
Thanks in advance!!! (1 Reply)
Discussion started by: Da Paper
1 Replies
5. UNIX for Advanced & Expert Users
How do you locate all nonblank lines that don't begin with #, /* ,or // ? (3 Replies)
Discussion started by: pulsar2587
3 Replies
6. Programming
hey all, I have question when am writing simple shell...
in the child am calling execvp, i want the parent to know when execvp returns - 1. how can i let the parent know the result of execvp
thanks in advance (9 Replies)
Discussion started by: joey
9 Replies
7. Homework & Coursework Questions
1.) I am to write scripts that will be phasetest folder in the home directory.
2.) The folder should have a set-up,phase and display files
I have written a small script which i used to check for the existing users and their password.
What I need help with:
I have a set of questions in a... (19 Replies)
Discussion started by: moraks007
19 Replies
8. UNIX for Dummies Questions & Answers
Hello,
I would like to know how we can highlight/select a section of a file in vi and delete that section if we don't want to use the dd command to delete one line at at time. There is one where we don't want to delete the whole line , but up to a certain word. (2 Replies)
Discussion started by: Pouchie1
2 Replies
LEARN ABOUT FREEBSD
pipe2
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