It is currently Mon, 23 Apr 2018 09:04:56 GMT

Author Message
 "broken pipe"

I'm putting the finishing touches on a shell I've written, and doing
so a query about signals came up.

It's generally the job of the shell to print abnormal termination
messages like "core dumped" and "segmentation violation". My shell
is no different. However, because I've seen the C shell report
broken pipes, whenever a process dies with SIGPIPE, my shell prints
"broken pipe" to the terminal. Unfortunately, broken pipes occur
more often than one would think. For example:

cat /usr/dict/words | sed 10q

causes cat to die with SIGPIPE.

My question is, does anyone know what the csh semantics are for
reporting a broken pipe; in other words, I'm looking for a reasonable
set of conditions under which to report a broken pipe, not just
when a sigpipe occurs.

Byron Rakitzis

 Sun, 18 Jul 1993 13:11:58 GMT   
   [ 1 post ] 

Similar Threads

1. TCP "Broken pipe" programming error

2. Help: host_access fails ("broken pipe")

3. "Broken pipe" when printing postscript files

4. "broken pipe" during GNOME configure

5. "Broken pipe" when decompressing

6. "broken pipe"

7. FTP to Linux yields "BROKEN PIPE"

8. "Broken Pipe" Problem

9. popen and "broken pipe"

10. Catching "Broken Pipes" in C

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software