The description of clientaddr= in nfs(5) is out of date and omits some
other typical reasons for using it. Let's start with this rewrite.
Signed-off-by: Chuck Lever <[email protected]>
---
utils/mount/nfs.man | 13 +++++++++----
1 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index e66daba..6dd1603 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -412,10 +412,15 @@ and
.IR tcp .
.TP 1.5i
.I clientaddr=n
-On a multi-homed client, this
-causes the client to use a specific callback address when
-communicating with an NFS version 4 server.
-This option is currently ignored.
+Specifies a single IPv4 address in dotted-quad form that the
+NFS client should advertise to a server for performing NFSv4
+callback requests for this mount point.
+If not specified, the mount command attempts to discover an
+appropriate callback address, then passes it to the NFS client.
+However, in the presence of multiple client network interfaces,
+special routing policies, or atypical network topologies, the
+exact address to use for callbacks may be difficult for the
+mount command to determine automatically.
.TP 1.5i
.I sec=mode
Same as \f3sec=mode\f1 for the nfs filesystem type (see above).
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Thu, Aug 30, 2007 at 03:48:10PM -0400, Chuck Lever wrote:
> +Specifies a single IPv4 address in dotted-quad form that the
> +NFS client should advertise to a server for performing NFSv4
> +callback requests for this mount point.
> +If not specified, the mount command attempts to discover an
> +appropriate callback address, then passes it to the NFS client.
> +However, in the presence of multiple client network interfaces,
> +special routing policies, or atypical network topologies, the
> +exact address to use for callbacks may be difficult for the
> +mount command to determine automatically.
Sounds good to me!
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On 08/30/2007 9:48:10 PM +0200, Chuck Lever <[email protected]> wrote:
> The description of clientaddr= in nfs(5) is out of date and omits some
> other typical reasons for using it. Let's start with this rewrite.
>
By the way, can we update the man page date show the current version
somewhere ? This is a bit disturbing to see "20 November 1993" at the
bottom of the man page, and would clear minds about the "ignored at this
time" or "not implemented yet" : does the word "currently" makes any
sense, when the only date showed is 15 years ago ?
Gabriel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
At 03:48 PM 8/30/2007, Chuck Lever wrote:
>+Specifies a single IPv4 address in dotted-quad form that the
>+NFS client should advertise to a server for performing NFSv4
NFSv4 client. Just to be clear.
>+callback requests for this mount point.
>+If not specified, the mount command attempts to discover an
>+appropriate callback address, then passes it to the NFS client.
NFSv4 server. Passing it to the "client" just means "kernel".
Doesn't count until the server gets it. :-)
>+However, in the presence of multiple client network interfaces,
>+special routing policies, or atypical network topologies, the
>+exact address to use for callbacks may be difficult for the
>+mount command to determine automatically.
"Difficult" doesn't actually say what happens. Perhaps:
... atypical network topologies, the ...
"server may not be able to establish a connection to the
address supplied by the client to use for callbacks. This in turn
may lead to degraded client NFSv4 operation."
Or, is that language too ominous?
Tom.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs