Bug 771876

Summary: nfs: nfs.addr-namelookup help needs to be updated
Product: [Community] GlusterFS Reporter: Saurabh <saujain>
Component: nfsAssignee: Vivek Agarwal <vagarwal>
Status: CLOSED CURRENTRELEASE QA Contact: Saurabh <saujain>
Severity: high Docs Contact:
Priority: high    
Version: pre-releaseCC: gluster-bugs, mzywusko, sankarshan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 13:56:08 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 817967    

Description Saurabh 2012-01-05 05:00:05 EST
Description of problem:
nfs.addr-namelookup help needs to be updated, the default value is off but the help says it is "on" in the last sentence.

Option: nfs.addr-namelookup
Default Value: (null)
Description: Users have the option of turning off name lookup for incoming client connections using this option. In some setups, the name server can take too long to reply to DNS queries resulting in timeouts of mount requests. Use this option to turn off name lookups during address authentication. Note, turning this off will prevent you from using hostnames in rpc-auth.addr.* filters. By default,  name lookup is on.

Version-Release number of selected component (if applicable):
glusterfs 3.3.0qa18 built on Dec 29 2011 01:49:17


How reproducible:

easily

Steps to Reproduce:
1.gluster volume set help
2.search for "nfs.addr-namelookup"
3.read the help
  
Actual results:
the status for default is on "By default,  name lookup is on."

Expected results:
"By default,  name lookup is off."

Additional info:
Comment 1 Anand Avati 2012-02-29 05:14:58 EST
CHANGE: http://review.gluster.com/2829 (nfs/doc: corrections) merged in master by Vijay Bellur (vijay@gluster.com)