> Looking at the code, we don't check WRITE_DATA for owner checks, only for > size or time changes. For owner/group changes, we check > FSAL_ACE_PERM_WRITE_OWNER, which is the correct ACL to check. > > Presumably, you could just add an ACL to all files allowing all access to your > "root" user. This should allow access, correct?
This would be a solution. > On 02/13/2017 09:31 AM, Satya Prakash GS wrote: > > Hi, > > > > Ganesha seems to be checking for FSAL_ACE_PERM_WRITE_DATA > permission > > to change owner/group perms (in the function > > fsal_check_setattr_perms). In our filesystem, there is another user > > who is equivalent to the root user. This user should be able to change > > owner/group of any file like the root user. Can somebody please > > explain the rationale behind this check and how our requirement of > > having another super user can be achieved. If you need a true additional super-user, Ganesha would really need to have code added to be able to configure such, and work to allow super-user privileges everywhere appropriate. What FSAL and what filesystem are you using? Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
