 |
 |
The xrootd protocol spec (v3.1.0) describes how `kXR_mkdir` and `kXR_open` operations both have an `options` field. In both cases, this field act as a bit mask for flags that affect the behaviour of the respective commands. According to the spec, both accept the value `kXR_mkpath` with similar semantics: `kXR_mkdir`: http://xrootd.org/doc/dev45/XRdv310.htm#_Toc464248821 `kXR_open`: http://xrootd.org/doc/dev45/XRdv310.htm#_Toc464248823 This is wrong as the xrootd code uses bit-0 in `kXR_mkdir` options to indicate parent directory elements should be created, whereas `kXR_open` uses bit-8 for the same behaviour. Therefore, the flags cannot be described using the same constant (`kXR_mkpath`). Further, these constants appear not to be defined anywhere in the spec. This makes the spec. incomplete. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/815 ######################################################################## 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