summaryrefslogtreecommitdiffstats
path: root/support/export/client.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2010-03-19 16:14:26 -0400
committerSteve Dickson <steved@redhat.com>2010-03-19 16:14:26 -0400
commit0935cebc1e130c6adfd870c88a6493277c84d47f (patch)
tree69a9e7010d10fdde499a727269eacb82c5a355f4 /support/export/client.c
parentbaa41b2c78e796540c45692ea35214f7090a78cb (diff)
downloadnfs-utils-0935cebc1e130c6adfd870c88a6493277c84d47f.tar.gz
nfs-utils-0935cebc1e130c6adfd870c88a6493277c84d47f.tar.xz
nfs-utils-0935cebc1e130c6adfd870c88a6493277c84d47f.zip
mount: Mount should retry unreachable hosts
Currently if a server is up but not responding (ie, it answers ARP requests, but not NFS or RPC requests), mount retries or backgrounds itself waiting for the server. If the server is not responding on the network at all, mount fails the mount request immediately. Users might find it more useful if mount retried in both cases. Note that this change means attempting to mount using a misspelled server name will "hang" for the retry amount. I suppose the error message isn't very helpful whether it fails immediately or waits a couple of minutes, though I imagine that an unreachable server is a much more common occurrence than a misspelling. Reported-by: Daniel Goering <g_daniel@gmx.net> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'support/export/client.c')
0 files changed, 0 insertions, 0 deletions