From 7b38a318a44fcf3fe1c18946c7c242ee9c3fd7d4 Mon Sep 17 00:00:00 2001 From: das Date: Sun, 29 Jun 2008 17:17:14 +0000 Subject: Make it clearer that it is possible to disable the generation of SIGPIPE for individual sockets (PR: kern/118626). While here, s/insure/ensure/. --- lib/libc/sys/socket.2 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'lib/libc/sys/socket.2') diff --git a/lib/libc/sys/socket.2 b/lib/libc/sys/socket.2 index 1cf3af8..c0028fa 100644 --- a/lib/libc/sys/socket.2 +++ b/lib/libc/sys/socket.2 @@ -168,7 +168,7 @@ and received as described in .Pp The communications protocols used to implement a .Dv SOCK_STREAM -insure that data +ensure that data is not lost or duplicated. If a piece of data for which the peer protocol has buffer space cannot be successfully transmitted @@ -187,11 +187,11 @@ roughly every minute in the absence of other activity. An error is then indicated if no response can be elicited on an otherwise idle connection for an extended period (e.g.\& 5 minutes). -A +By default, a .Dv SIGPIPE signal is raised if a process sends -on a broken stream; this causes naive processes, -which do not handle the signal, to exit. +on a broken stream, but this behavior may be inhibited via +.Xr setsockopt 2 . .Pp .Dv SOCK_SEQPACKET sockets employ the same system calls -- cgit v1.1