 |
 |
I don't know the reason for that but maybe you are better of using the native XROOTD way e.g. all files are owned by xrootd in the back you define the access restrictions via the auth DB file. (our auth library has some security implications one must be aware of!) In your auth db you can just define rules by users like: # every use has a private directory u foo /data/foo/ a u bar /data/bar/ a # all the xrootd group members share read permission g xrootd /data/ r and that should give exactly the behaviour you were describing ... But maybe I don't understand fully your use case. You want to change files only via XROOTD or also on the back on the file system via some other mechanism? Cheers Andreas. On Fri, Apr 24, 2015 at 9:26 PM, Marcel Kuriyama <[log in to unmask]> wrote: > Xrootd is still the owner of all files and folders. > And any user can create and delete files in any user folder. > > Maybe I must remove all users from the xrootd group. > > — > Reply to this email directly or view it on GitHub > <https://github.com/xrootd/xrootd/issues/230#issuecomment-96041745>. > > ------------------------------ > > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-DEV list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1 > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1