mschorm / rpms / util-linux

Forked from rpms/util-linux 2 years ago
Clone
859b4d5
--- util-linux-2.12p/mount/mount.8.nfsdoc	2005-05-10 11:46:25.119592000 -0400
859b4d5
+++ util-linux-2.12p/mount/mount.8	2005-10-07 09:46:13.374277000 -0400
859b4d5
@@ -1339,29 +1339,17 @@ For details, see
859b4d5
 
859b4d5
 Especially useful options include
859b4d5
 .TP
859b4d5
-.B rsize=8192,wsize=8192
859b4d5
-This will make your nfs connection faster than with the default
859b4d5
-buffer size of 4096. (NFSv2 does not work with larger values of
859b4d5
-.B rsize
859b4d5
-and
859b4d5
-.BR wsize .)
859b4d5
-.TP
859b4d5
-.B hard
859b4d5
-The program accessing a file on a NFS mounted file system will hang
859b4d5
-when the server crashes. The process cannot be interrupted or
859b4d5
-killed unless you also specify
859b4d5
-.BR intr .
859b4d5
-When the NFS server is back online the program will continue undisturbed
859b4d5
-from where it was. This is probably what you want.
859b4d5
-.TP
859b4d5
-.B soft
859b4d5
-This option allows the kernel to time out if the nfs server is not
859b4d5
-responding for some time. The time can be
859b4d5
-specified with
859b4d5
-.BR timeo=time .
859b4d5
-This option might be useful if your nfs server sometimes doesn't respond
859b4d5
-or will be rebooted while some process tries to get a file from the server.
859b4d5
-Usually it just causes lots of trouble.
859b4d5
+.B rsize=32768,wsize=32768
859b4d5
+This causes the NFS client to try to negotiate a buffer size
859b4d5
+up to the size specified.
859b4d5
+A large buffer size does improve performance, but both the 
859b4d5
+server and client have to support it.
859b4d5
+In the case where one of these does not support the size specified, 
859b4d5
+the size negotiated will be the largest that both support.
859b4d5
+.TP
859b4d5
+.B intr
859b4d5
+This will allow NFS operations (on hard mounts) to be 
859b4d5
+interrupted while waiting for a response from the server. 
859b4d5
 .TP
859b4d5
 .B nolock
859b4d5
 Do not use locking. Do not start lockd.
859b4d5
@@ -1408,30 +1396,16 @@ For details, see
859b4d5
 Especially useful options include
859b4d5
 .TP
859b4d5
 .B rsize=32768,wsize=32768
859b4d5
-This will make your NFS connection faster than with the default
859b4d5
-buffer size of 4096.
859b4d5
-.TP
859b4d5
-.B hard
859b4d5
-The program accessing a file on a NFS mounted file system will hang
859b4d5
-when the server crashes. The process cannot be interrupted or
859b4d5
-killed unless you also specify
859b4d5
-.BR intr .
859b4d5
-When the NFS server is back online the program will continue undisturbed
859b4d5
-from where it was. This is probably what you want.
859b4d5
-.TP
859b4d5
-.B soft
859b4d5
-This option allows the kernel to time out if the NFS server is not
859b4d5
-responding for some time. The time can be
859b4d5
-specified with
859b4d5
-.BR timeo=time .
859b4d5
-This timeout value is expressed in tenths of a second.
859b4d5
-The
859b4d5
-.BR soft
859b4d5
-option might be useful if your NFS server sometimes doesn't respond
859b4d5
-or will be rebooted while some process tries to get a file from the server.
859b4d5
-Avoid using this option with
859b4d5
-.BR proto=udp
859b4d5
-or with a short timeout.
859b4d5
+This causes the NFS4 client to try to negotiate a buffer size
859b4d5
+up to the size specified.
859b4d5
+A large buffer size does improve performance, but both the 
859b4d5
+server and client have to support it.
859b4d5
+In the case where one of these does not support the size specified, 
859b4d5
+the size negotiated will be the largest that both support.
859b4d5
+.TP
859b4d5
+.B intr
859b4d5
+This will allow NFS4 operations (on hard mounts) to be 
859b4d5
+interrupted while waiting for a response from the server. 
859b4d5
 
859b4d5
 .SH "Mount options for ntfs"
859b4d5
 .TP