No the server is ran like xrootd-privileged and cmsd-privileged as a service.

As you say, the permissions should be that only I (lavezzo) can see this folder: but I would expect that the xrootd-multiuser, being able to recognize me as lavezzo, it would then give me permissions to see my own stuff. Alternatively, is there a way to force new directories created via xrdfs mkdir to have more loose permissions by default? Because at the moment if you create a directory with xrdfs mkdir, put files in it, you can't xrdfs ls, which is breaking some things for us.

umask is 0002. And at the moment we have multiuser.umask 0022 configured.

I tried running it with strace but I either did it wrong, or nothing interesting came out just things like

futex(0x613f08, FUTEX_WAKE_PRIVATE, 1)  = 1
futex(0x7ffc4ef90630, FUTEX_WAIT_PRIVATE, 0, NULL

I don't know if it's a bug in xrootd, xrootd-multiuser, or some misconfiguration on our end, but it would be great to understand that's going on and I thank you for the help in doing so!


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/2069/1670008733@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/2069#issuecomment-1670008733", "url": "https://github.com/xrootd/xrootd/issues/2069#issuecomment-1670008733", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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