 |
 |
Hi, it was set because it is in a shared file system that is not managed by xrootd. I wanted to have ownership other than xrootd and to have proper ACL's. Doug On 01/10/2015 02:13 AM, Andrew Hanushevsky wrote: > > Hi Doug, > > Correct, the sticky bit is used by xrootd to indicate that the file is incomplete (i.e. pending to be staged or some other action that requires file completion). So, when you open such a file, the xrootd will stall the client until the sticky bit is turned off (as you see in the log). In your case, that will never happen because it was manually set on. Why did you do that anyway? > > Andy > > — > Reply to this email directly or view it on GitHub <https://github.com/xrootd/xrootd/issues/189#issuecomment-69448165>. > --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/189#issuecomment-69453150 ######################################################################## 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