If you don't want your program to be killed by SIGPIPE, just ignore it.
Then you'll start getting write() errors instead of being killed.
SIGPIPE is designed for situations like this:
head prints the first 10 lines and quits, closing its half of the pipe. With it gone, there's no further reason for cat to continue existing. cat tries to write to the broken pipe, and gets cleanly knocked out by SIGPIPE instead of freaking out with write errors.
Last edited by Corona688; 07-14-2011 at 02:47 PM..
Reason: socket.h should be signal.h
Hi there,
I try to use:
> find * | ls
but it just gave me one level of ' ls '. and it said:
> find * | ls
dir1 dir2 f1 f2 f3
Broken Pipe
>
what is broken pipe?
how can i fix it?
thks
Gusla (3 Replies)
sometimes I ftp files from an Unix environment from the command prompt of my win2000 pc and I get a "broken pipe" message. sometimes I'll get nothing but sometimes I'll get part of the file.
Whats this "broken pipe" about?? (3 Replies)
Hello everyone
I got a school project that was due yesterday so i really would aprreciate some help
the following is an example of the input file (bateriaTestes)
1 caeiro 2000 d
2 pessoa 100 w
3 campos 200 b
4 soares 500 w
simple 4 field lines. lines separated by \n and fields by... (1 Reply)
Hi
I tried to open the man page of sh and piped to `pg`. Normally while reading a file page by page using `pg`, if we wanna quit at the middle of file, we give "q" near the colon mode.
Ex1: $cat file1 | pg
hi
how
r
u
: (page1) now press "return key", it will go to next page
yes
i ... (1 Reply)
Hi
I tried to open the man page of sh and piped to `pg`. Normally while reading a file page by page using `pg`, if we wanna quit at the middle of file, we give "q" near the colon mode.
Ex1: $cat file1 | pg
hi
how
r
u
: (page1) now press "return key", it will go to next page
yes
i ... (3 Replies)
hi
i have a server, and i have a web site and i installed apache in the /usr/local/apache/logs
i have a file and i have this problem
(32)Broken pipe: core_output_filter: writing data to the network
plz help me how i can resolve this
plz it's urgent
th (1 Reply)
hi
i am trying to upload a file using ftp protocol,
i am facing some problem while uploading
"Failedtoupload:SFTREGUP1:FTP_ASCII_MAILBOX21.39.10.856305000:Broken pipe"
Can someone explain why it is coming , and the solution . (0 Replies)
I know what causes 'broken pipe' errors, but I can't understand why I can get it (only occasionally) with my example:
ps -ef | grep "\./ans$" | grep -v grep
Basically I'm searching the ps output looking for the process I'm interested in and excluding the process that is grepping for the... (2 Replies)
Hi all,
I am trying to run a sleep command and I am receiving a broken pipe when I execute. any help would be greatly appreciated.
sleep `< /dev/urandom tr -dc 0-6 | head -c2` (2 Replies)
Discussion started by: gartie
2 Replies
LEARN ABOUT OSX
pipe
PIPE(2) BSD System Calls Manual PIPE(2)NAME
pipe -- create descriptor pair for interprocess communication
SYNOPSIS
#include <unistd.h>
int
pipe(int fildes[2]);
DESCRIPTION
The pipe() function creates a pipe (an object that allows unidirectional data flow) and allocates a pair of file descriptors. The first
descriptor connects to the read end of the pipe; the second connects to the write end.
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 pro-
gram: the source's standard output is set up to be the write end of the pipe; the sink's standard input is set up to be the read end of the
pipe. The pipe itself persists until all of its associated descriptors are closed.
A pipe whose read or write end has been 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 generation of the SIGPIPE signal can be suppressed using the F_SETNOSIGPIPE fcntl command.
RETURN VALUES
On successful creation of the pipe, zero is returned. Otherwise, a value of -1 is returned and the variable errno set to indicate the error.
ERRORS
The pipe() call will fail if:
[EFAULT] The fildes buffer is in an invalid area of the process's address space.
[EMFILE] Too many descriptors are active.
[ENFILE] The system file table is full.
SEE ALSO sh(1), fork(2), read(2), socketpair(2), fcntl(2), write(2)HISTORY
A pipe() function call appeared in Version 6 AT&T UNIX.
4th Berkeley Distribution February 17, 2011 4th Berkeley Distribution