 |
 |
Thank very much for your help. Just to confirm, the best way to handle this is in xrootd itself, rather than changes to the xrootd-hdfs (and other) plugins? We'd be happy to test the change at Nebraska. I'd guess 6143f879290fa12739c5eaa466941acddfd57067 is the only commit necessary? No other plugin or config changes? Also, I'd attempted to use the compatibility flag with v5.0.2: ```diff -ofs.osslib /usr/lib64/libXrdHdfs.so +ofs.osslib +mmapio /usr/lib64/libXrdHdfs.so ``` It seemed to work as expected for xrootd, but seemed to run into a config parsing issue in cmsd: ``` Plugin osslib +mmapio-5 not found; falling back to using +mmapio Plugin No such file or directory loading osslib +mmapio ------ [log in to unmask] phase 2 server initialization failed. 201120 09:45:34 8041 XrdProtocol: Protocol cms could not be loaded ------ cmsd [log in to unmask]:1094 initialization failed. ``` -- 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/1331#issuecomment-731255627 ######################################################################## 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