Date: Sat, 20 Aug 2011 11:10:16 GMT From: Catalin Nicutar <cnicutar@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 197907 for review Message-ID: <201108201110.p7KBAGHk022458@skunkworks.freebsd.org>
index | next in thread | raw e-mail
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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201108201110.p7KBAGHk022458>