@olifre - coming back to this.

Can you please share your partial fix via a PR? I'd like to see it go in simply because it iterates us toward a better implementation.

We've found there's a number of places where HTTP-style operations or WLCG token authorization maps poorly to POSIX. Where we can, we aim for practical solutions. I could see where we might need to do something that has a race condition (e.g., check for file existence then create a file) but is "mostly correct".

@abh3 - to some extent, the WLCG token authorizations are more fine grained than what's in XRootD. What are your thoughts on adding two new finer-grained authorization levels in XRootD?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1655#issuecomment-1114051565", "url": "https://github.com/xrootd/xrootd/issues/1655#issuecomment-1114051565", "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