From owner-p4-projects@FreeBSD.ORG  Sat Aug 20 11:10:18 2011
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 82E16106564A; Sat, 20 Aug 2011 11:10:17 +0000 (UTC)
Delivered-To: perforce@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2CC0C106566C
	for <perforce@freebsd.org>; Sat, 20 Aug 2011 11:10:17 +0000 (UTC)
	(envelope-from cnicutar@freebsd.org)
Received: from skunkworks.freebsd.org (skunkworks.freebsd.org
	[IPv6:2001:4f8:fff6::2d])
	by mx1.freebsd.org (Postfix) with ESMTP id 1A3828FC12
	for <perforce@freebsd.org>; Sat, 20 Aug 2011 11:10:17 +0000 (UTC)
Received: from skunkworks.freebsd.org (localhost [127.0.0.1])
	by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id p7KBAGpQ022461
	for <perforce@freebsd.org>; Sat, 20 Aug 2011 11:10:16 GMT
	(envelope-from cnicutar@freebsd.org)
Received: (from perforce@localhost)
	by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id p7KBAGHk022458
	for perforce@freebsd.org; Sat, 20 Aug 2011 11:10:16 GMT
	(envelope-from cnicutar@freebsd.org)
Date: Sat, 20 Aug 2011 11:10:16 GMT
Message-Id: <201108201110.p7KBAGHk022458@skunkworks.freebsd.org>
X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to
	cnicutar@freebsd.org using -f
From: Catalin Nicutar <cnicutar@FreeBSD.org>
To: Perforce Change Reviews <perforce@freebsd.org>
Precedence: bulk
Cc: 
Subject: PERFORCE change 197907 for review
X-BeenThere: p4-projects@freebsd.org
X-Mailman-Version: 2.1.5
List-Id: p4 projects tree changes <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 11:10:18 -0000

http://p4web.freebsd.org/@@197907?ac=10

Change 197907 by cnicutar@cnicutar_cronos on 2011/08/20 11:10:09

	Change tcp(4) to reflect the updated semantics of TCP_RCVUTO_TIMEOUT.

Affected files ...

.. //depot/projects/soc2011/cnicutar_tcputo_9/src/share/man/man4/tcp.4#3 edit

Differences ...

==== //depot/projects/soc2011/cnicutar_tcputo_9/src/share/man/man4/tcp.4#3 (text+ko) ====

@@ -237,11 +237,14 @@
 This option is silently left out if (due to other options) not enough space
 is available.
 .It Dv TCP_RCVUTO_TIMEOUT
-By setting this option to a value larger than 1 the user allows a TCP to
-accept the timeout suggestion sent by the peer.
+When setting this value to 1, the application specifies any value (up to
+.Dv uto.max_timeout
+) is acceptable.
+If the application specifies a value larger than 1, that is considered
+the maximum acceptable timeout for the connection.
 The default value is 0.
-By getting this option the user can determine the actual timeout (in seconds)
-as advertised by the peer.
+By retriving this option the user can determine the actual timeout (in
+seconds) advertised by the peer.
 .Pp
 When using both
 .Dv TCP_RCVUTO_TIMEOUT
@@ -254,9 +257,9 @@
 .Xr getsockopt 2
 the most recent value received is returned.
 .Pp
-A possible use of this option is allowing a user to request a large timeout
+A possible use of this option is allowing a peer to request a large timeout
 (several hours) for a connection.
-Even if the user is offline for long periods of time the connection will be
+Even if the peer is offline for long periods of time the connection will be
 maintained.
 .Pp
 This option has security implications.