Differences between version 3 and previous revision of SIGPIPE.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Tuesday, October 29, 2002 8:40:24 pm | by JohnMcPherson | Revert |
| Older page: | version 2 | Last edited on Monday, October 28, 2002 9:39:12 pm | by JohnMcPherson | Revert |
@@ -3,5 +3,5 @@
This signal is raised when a program writes to a socket or fifo that has no readers. The default action of this signal is to cause the program to terminate.
You might see this message if you have a series of commands in a shell pipe line and one of the processes quits. Eg:
$ cat somefile | head
-After "head" has printed out the first 10 lines and quits, "cat" will get a pipe error. However, cat catches the signal and quits gracefully. If you use
cvs, then you might see the shell print out a message as cvs doesn't handle this signal gracefully.
+After "head" has printed out the first 10 lines and quits, "cat" will get a pipe error. However, cat catches the signal and quits gracefully. If you pipe the output of some
cvs(1) commands into less(1) and quit
, then you might see the shell print out a message as cvs doesn't handle this signal gracefully.
