Hi Andy, the problem is SFS_O_RDONLY = 0. When a "open for write" flag such as kXR_open_apnd is sent to an XRootD server it is translated to SFS_O_RDONLY. Here at CERN we are marking files within our tape backed directories as "NOT updateable". This is an EOS specific ACL. Such files should be read-only once they have been created. An "open for write" on such files including the use of the kXR_open_apnd flag should fail either with a permissions error or with a "not supported error". In order for us to detect kXR_open_apnd it must be passed through to XrdSfsFile::open() in some way. Ignoring it and passing SFS_O_RDONLY is not correct. Removing the kXR_open_apnd flag all together is another solution.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1126?email_source=notifications\u0026email_token=AA7NRDXN3R3K6AFDECTUUR3RAKDSFA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKCDJI#issuecomment-580133285", "url": "https://github.com/xrootd/xrootd/issues/1126?email_source=notifications\u0026email_token=AA7NRDXN3R3K6AFDECTUUR3RAKDSFA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKCDJI#issuecomment-580133285", "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