I have restarted multiple times but it is not changing I am not able to see nfs_acl in my environment.
To file the bug what I need to do? Regards, Abhishek On Wed, May 4, 2016 at 1:28 PM, Soumya Koduri <skod...@redhat.com> wrote: > Even on my setup if I change nfs.port, all the other services also started > registering on those ports. Can you please file a bug for it. > That seems like a bug (or is it intentional..Niels?). > > 100005 3 tcp 2049 mountd > 100005 1 tcp 2049 mountd > 100003 3 tcp 2049 nfs > 100021 4 tcp 2049 nlockmgr > 100227 3 tcp 2049 nfs_acl > > However, as you can see NFSACL did come up. Try restarting volume > " gluster v start <volname> force" and check your logs again. > > Thanks, > Soumya > > > On 05/04/2016 12:29 PM, ABHISHEK PALIWAL wrote: > >> i am changing the nfs.port using gluster volume set gv0 nfs.port 2049 >> but it automatically changing MOUNTD as well >> >> and nfs.disable is also off >> >> gluster volume get gv0 nfs.disable >> Option Value >> ------ ----- >> nfs.disable off >> >> >> >> -- Regards Abhishek Paliwal
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users