From: Chuck Lever Subject: [PATCH] mount.nfs: Update description of clientaddr= in nfs(5) Date: Thu, 30 Aug 2007 15:48:10 -0400 Message-ID: <20070830194810.4524.58037.stgit@monet.1015granger.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: nfs@lists.sourceforge.net Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IQr1p-0007KR-BQ for nfs@lists.sourceforge.net; Thu, 30 Aug 2007 13:54:13 -0700 Received: from flpvm23.prodigy.net ([207.115.20.53]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1IQq0c-0003n5-Tu for nfs@lists.sourceforge.net; Thu, 30 Aug 2007 12:48:59 -0700 Received: from monet.1015granger.net (adsl-76-241-169-38.dsl.sfldmi.sbcglobal.net [76.241.169.38]) by flpvm23.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id l7UJmQNf009768 for ; Thu, 30 Aug 2007 12:48:28 -0700 Received: from monet.1015granger.net (monet.1015granger.net [127.0.0.1]) by monet.1015granger.net (8.14.1/8.14.1) with ESMTP id l7UJmAT6004540 for ; Thu, 30 Aug 2007 15:48:11 -0400 List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net 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 --- 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 - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs