diff options
| author | NeilBrown <neilb@suse.com> | 2016-08-03 12:55:36 -0400 |
|---|---|---|
| committer | Steve Dickson <steved@redhat.com> | 2016-08-03 14:24:16 -0400 |
| commit | 7ebf6d00315faf3cc9e17dbdfdf28220788968ac (patch) | |
| tree | 97699ddbf485e04d5f0599aae68153935942f466 /support/export/client.c | |
| parent | d4b2d066b0dac218fbd1471492b7575d55a413e5 (diff) | |
| download | nfs-utils-7ebf6d00315faf3cc9e17dbdfdf28220788968ac.tar.gz nfs-utils-7ebf6d00315faf3cc9e17dbdfdf28220788968ac.tar.xz nfs-utils-7ebf6d00315faf3cc9e17dbdfdf28220788968ac.zip | |
nfs.man: clarify effect of 'retry' option
The total timeout for a "mount" attempt to a non-responsive server
will always be a multiple of the time a single mount attempt in the
kernel takes, which for TCP defaults to about 4 minutes.
The documentation for the "retry" option seems to suggest that this can
be used
to set a maximum but it really sets a time after which to stop retrying.
The total can be as much as "retry" plus the time for a single attempt.
So clarify the documentation a bit, and also note that retrans
defaults are different for UDP and TCP:
#define NFS_DEF_UDP_RETRANS (3)
#define NFS_DEF_TCP_RETRANS (2)
Reported-by: Howard Guo<hguo@suse.com>
Acked-by: J. Bruce Fields <bfields@fieldses.org>
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'support/export/client.c')
0 files changed, 0 insertions, 0 deletions