We have no protocols which require explicit confirmation

1 files changed, 2 insertions, 25 deletions

diff --git a/lib/libc/sys/accept.2 b/lib/libc/sys/accept.2
index e043f79bd63..5ac01c80ebf 100644
--- a/lib/libc/sys/accept.2
+++ b/lib/libc/sys/accept.2
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: accept.2,v 1.27 2014/08/31 01:42:36 guenther Exp $
+.\"	$OpenBSD: accept.2,v 1.28 2014/09/09 03:50:43 guenther Exp $
 .\"	$NetBSD: accept.2,v 1.7 1996/01/31 20:14:42 mycroft Exp $
 .\"
 .\" Copyright (c) 1983, 1990, 1991, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)accept.2	8.2 (Berkeley) 12/11/93
 .\"
-.Dd $Mdocdate: August 31 2014 $
+.Dd $Mdocdate: September 9 2014 $
 .Dt ACCEPT 2
 .Os
 .Sh NAME
@@ -125,29 +125,6 @@ or
 a socket for the purposes of doing an
 .Fn accept
 by selecting it for read.
-.Pp
-For certain protocols which require an explicit confirmation,
-.Fn accept
-can be thought of as merely dequeuing the next connection
-request and not implying confirmation.
-Confirmation can be implied by a normal read or write on the new file
-descriptor, and rejection can be implied by closing the new socket.
-.Pp
-One can obtain user connection request data without confirming
-the connection by issuing a
-.Xr recvmsg 2
-call with an
-.Fa msg_iovlen
-of 0 and a non-zero
-.Fa msg_controllen ,
-or by issuing a
-.Xr getsockopt 2
-request.
-Similarly, one can provide user connection rejection information
-by issuing a
-.Xr sendmsg 2
-call providing only the control information, or by calling
-.Xr setsockopt 2 .
 .Sh RETURN VALUES
 The call returns \-1 on error.
 If it succeeds, it returns a non-negative integer that is a descriptor