From: "Talpey, Thomas" Subject: Re: [PATCH] mount.nfs: Update description of clientaddr= in nfs(5) Date: Thu, 30 Aug 2007 21:35:30 -0400 Message-ID: References: <20070830194810.4524.58037.stgit@monet.1015granger.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: Chuck Lever 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 1IQvQF-0008Jo-CN for nfs@lists.sourceforge.net; Thu, 30 Aug 2007 18:35:43 -0700 Received: from mx2.netapp.com ([216.240.18.37]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1IQvQI-0000EA-QO for nfs@lists.sourceforge.net; Thu, 30 Aug 2007 18:35:48 -0700 In-Reply-To: <20070830194810.4524.58037.stgit@monet.1015granger.net> References: <20070830194810.4524.58037.stgit@monet.1015granger.net> 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 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 - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs