From baf04c05bdeb97d014a048c4e531a5cc36ce1fd0 Mon Sep 17 00:00:00 2001 From: Max Matveev Date: Tue, 30 Aug 2011 08:40:33 -0400 Subject: [PATCH] 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 --- utils/mount/nfs.man | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) 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 -- 2.39.5