Well, I think we have a philosophical difference. If we remove the flag <br>
definition from the client interface that should suffice, as it cannot be <br>
specified unless you subvert the system. Having the unsupported append <br>
converted to a read is certainly a safe option though you won&#39;t get what <br>
you wanted, then again, he server doesn&#39;t support append. Frankly, other <br>
that semantics here I don&#39;t see what the real problem is as you shouldn&#39;t <br>
be speciying append if it isn&#39;t supported and if you do it will back down <br>
to something that is prefectly safe.<br>
<br>
On Thu, 30 Jan 2020, murrayc3 wrote:<br>
<br>
&gt; Hi Andy, the problem is SFS_O_RDONLY = 0.  When a &quot;open for write&quot; 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 &quot;NOT updateable&quot;.  This is an EOS specific ACL.  Such files should be read-only once they have been created.  An &quot;open for write&quot; on such files including the use of the kXR_open_apnd flag should fail either with a permissions error or with a &quot;not supported error&quot;.  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.<br>
&gt;<br>
&gt; -- <br>
&gt; You are receiving this because you commented.<br>
&gt; Reply to this email directly or view it on GitHub:<br>
&gt; https://github.com/xrootd/xrootd/issues/1126#issuecomment-580133285<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/xrootd/xrootd/issues/1126?email_source=notifications&amp;email_token=AA7NRDSGP4DM2XBUNBA57BTRAKFUHA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKDR4I#issuecomment-580139249">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AA7NRDUPRUMQCIUCOIGLL5TRAKFUHANCNFSM4KMSSLUA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AA7NRDSX7JEEGUD6CH6CPSTRAKFUHA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKDR4I.gif" height="1" width="1" alt="" /></p>
<!cript type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1126?email_source=notifications\u0026email_token=AA7NRDSGP4DM2XBUNBA57BTRAKFUHA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKDR4I#issuecomment-580139249",
"url": "https://github.com/xrootd/xrootd/issues/1126?email_source=notifications\u0026email_token=AA7NRDSGP4DM2XBUNBA57BTRAKFUHA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKDR4I#issuecomment-580139249",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
<br>
<hr>
<p align="left">
Use REPLY-ALL to reply to list</p>
<p align="center">To unsubscribe from the XROOTD-DEV list, click the following link:<br>
<a href="https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1" target="_blank">https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1</a>
</p>