 |
 |
Hi Brian, By default, POSC is only available when specifically requested. But, es, it does get setup so cleanup will also occur (though, there shouldn't be anything to cleanup). If you don't want it, simply say ofs.persist off http://xrootd.org/doc/dev48/ofs_config.htm#_Toc401930722 Andy On Sun, 30 Sep 2018, Brian P Bockelman wrote: > This is actually the HDFS backend - but, logically, it works the same way as `setfsuid`. The HDFS client is setup to be able to impersonate any HDFS user. > > Honestly, I don't _want_ to support POSC since, as you point out, it really isn't plausible to "do it right" in this configuration. > > Rather than trying to fix something that is fundamentally unfixable, is it possible to return an error or otherwise disable POSC? For me, the bigger problem is someone who starts a POSC transfer can cause my server to be unable to restart. > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/830#issuecomment-425761935 -- 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/830#issuecomment-426011103 ######################################################################## 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