[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix the log message

>From : supriti.si...@suse.com has uploaded a new change for review. ( https://review.gerrithub.io/350650 Change subject: Fix the log message .. Fix the log message Change-Id:

Re: [Nfs-ganesha-devel] ganesha config editor user interface thoughts

Malahal Naineni wrote on Sat, Feb 25, 2017 at 03:33:17PM +0530: > - All config is in blocks > - Most blocks are unique with their tag names > - exceptions: "export" and "client" blocks. > - "export" is unique by "path" value More like unique by pseudo path; path can be identical for various

Re: [Nfs-ganesha-devel] ganesha config editor user interface thoughts

Based on Sriram's options idea: "ganesha_config set blocknames [sub-blocknames] --parameter value" will created block/subblocks if doesn't exist and will add the given parameter values inside the block. For example, "ganesha_config set NFS_CORE_PARAM --MNT_port " will create nfs_core_param

Re: [Nfs-ganesha-devel] file lock requests hang on nfs client

My bad. Thought I had it covered. But, a restart changed the port (Fixed it by using NLM_Port config option). Thanks for the help. On Sun, Feb 26, 2017 at 11:33 PM, Soumya Koduri wrote: > Do you have firewalld/iptables enabled? If yes, you may need to unblock > the ports