Differences between version 4 and revision by previous author of SIGPIPE.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Monday, March 1, 2004 7:35:41 am | by GrahamBreed | Revert |
| Older page: | version 3 | Last edited on Tuesday, October 29, 2002 8:40:24 pm | by JohnMcPherson | Revert |
@@ -4,4 +4,6 @@
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 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.
+
+If you get this message when writing to a socket, it can be avoided by passing [MSG_NOSIGNAL] as a flag to send().
