From: Max Matveev Date: Tue, 30 Aug 2011 12:40:33 +0000 (-0400) Subject: Update nfs(5) manpage - timeo for NFS/TCP X-Git-Tag: debian/1%1.2.5-1~11^2~21 X-Git-Url: https://git.decadent.org.uk/gitweb/?p=nfs-utils.git;a=commitdiff_plain;h=baf04c05bdeb97d014a048c4e531a5cc36ce1fd0;ds=sidebyside Update nfs(5) manpage - timeo for NFS/TCP NFS/TCP does linear backoff then retransmiting - the manpage was mistakenly asserting the "no backoff" theory. Signed-off-by: Max Matveev Signed-off-by: Jim Rees Signed-off-by: Steve Dickson --- diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man index dfb0bc9..ce40933 100644 --- a/utils/mount/nfs.man +++ b/utils/mount/nfs.man @@ -112,12 +112,16 @@ option may mitigate some of the risks of using the option. .TP 1.5i .BI timeo= n -The time (in tenths of a second) the NFS client waits for a -response before it retries an NFS request. If this -option is not specified, requests are retried every -60 seconds for NFS over TCP. -The NFS client does not perform any kind of timeout backoff -for NFS over TCP. +The time in deciseconds (tenths of a second) the NFS client waits for a +response before it retries an NFS request. +.IP +For NFS over TCP the default +.B timeo +value is 600 (60 seconds). +The NFS client performs linear backoff: After each retransmission the +timeout is increased by +.BR timeo +up to the maximum of 600 seconds. .IP However, for NFS over UDP, the client uses an adaptive algorithm to estimate an appropriate timeout value for frequently used