[PATCH 0/9] More mount.nfs clean-ups

[PATCH 0/9] More mount.nfs clean-ups

[Chuck Lever]

These patches clean up various hacks that were introduced with the recently
added text-based mount logic.  The biggest change is to improve the way the
'addr=' and 'clientaddr=' mount options are handled.

-- 
corporate:    <chuck dot lever at oracle dot com>

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

Re: [PATCH 0/9] More mount.nfs clean-ups

[Neil Brown]

On Friday August 24, chuck.lever@oracle.com wrote:
> These patches clean up various hacks that were introduced with the recently
> added text-based mount logic.  The biggest change is to improve the way the
> 'addr=' and 'clientaddr=' mount options are handled.

All applied, thanks.

NeilBrown

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

Re: [PATCH 0/9] More mount.nfs clean-ups

[Chuck Lever]

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

Neil Brown wrote:
> On Friday August 24, chuck.lever@oracle.com wrote:
>> These patches clean up various hacks that were introduced with the recently
>> added text-based mount logic.  The biggest change is to improve the way the
>> 'addr=' and 'clientaddr=' mount options are handled.
> 
> All applied, thanks.

Thanks.  Jeff gave a good reason that I hadn't considered to allow 
sysadmins to specify clientaddr=, so I will probably be sending a patch 
that "reverts" the clientaddr= change.

And I'll make a note of the clientaddr= firewall requirement here:

http://wiki.linux-nfs.org/wiki/index.php/NewMountDesignSpec

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