summaryrefslogtreecommitdiffstats
path: root/utils/mount/nfs.man
diff options
context:
space:
mode:
authorMax Matveev <makc@redhat.com>2011-08-30 08:40:33 -0400
committerSteve Dickson <steved@redhat.com>2011-08-30 08:40:33 -0400
commit5af7eb76b210cc15fc4b8d7d03a669353997b827 (patch)
tree18c0e01d1526715ed1b36416158ea56377d01fe2 /utils/mount/nfs.man
parentbbd9f5a98c3a401371bc642ac8545b1ccfeeab4d (diff)
downloadnfs-utils-5af7eb76b210cc15fc4b8d7d03a669353997b827.tar.gz
nfs-utils-5af7eb76b210cc15fc4b8d7d03a669353997b827.tar.xz
nfs-utils-5af7eb76b210cc15fc4b8d7d03a669353997b827.zip
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 <makc@redhat.com> Signed-off-by: Jim Rees <rees@umich.edu> Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/mount/nfs.man')
-rw-r--r--utils/mount/nfs.man16
1 files 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