12-18-2006
The error messages aren't trick questions. It sounds like file.tmp, or some other file your program was using, is a pipe, a pipe which closes on the other end while your program is still using it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: eloquent99
3 Replies
2. UNIX for Advanced & Expert Users
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)
Discussion started by: ramkrix
1 Replies
3. UNIX for Dummies Questions & Answers
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)
Discussion started by: ramkrix
3 Replies
4. Linux
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 (2 Replies)
Discussion started by: abir2
2 Replies
5. Shell Programming and Scripting
Hi All ,
Is there any way to replace the pipe ( | ) with the broken pipe (0xA6) in unix (1 Reply)
Discussion started by: saj
1 Replies
6. UNIX for Dummies Questions & Answers
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)
Discussion started by: fhew
2 Replies
7. UNIX for Advanced & Expert Users
The "write failed: Broken pipe" message is reported by the file sending PC which run my writed network device driver while 500MB or 900MB is sended!
What does the message mean? Does this mean there is a bug in my driver?
li,kunlun (11 Replies)
Discussion started by: liklstar
11 Replies
8. Red Hat
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
9. Shell Programming and Scripting
Hello,
I am trying to run some code on Matlab over ssh . The code takes around 5-6 hours to complete. so after giving the command to run it , I locked my machine and then went off to sleep at night, only to discover in the morning that I get this message :
...Code running, partial results... (1 Reply)
Discussion started by: ajayram
1 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I am iseries resource and having Issue in one of the sFTP failures between one of my job (Unix --> iSeries).
The response to sending machine (Unix) is "Write Failed Broken Pipe".
Appreciate any help Available on why this Issue happens, how can we replicate the same, what fixes can... (1 Reply)
Discussion started by: hamelchauhan
1 Replies
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