Re: [PATCH] mount.nfs: Update description of clientaddr= in nfs(5)

[Chuck Lever <chuck.lever@oracle.com>]

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

Talpey, Thomas wrote:
> At 03:48 PM 8/30/2007, Chuck Lever wrote:
>> +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."

I think detailing the consequences a little is a good idea, so I'll try 
to work this in.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs