So, thinking a bit more about it. To make this work in R5 you need to use the actual protocol name in the directive (i.e. "xroot") otherwise we get a double load issue. That is solved in R5.1 but that doesn't help you now. So, in the end the safest approach is to not specify "xrd.protocol xrootd *" directive no matter the context. Once you are using 5.1.0 then you can safely do it (use "xroot" protocol to avoid nasty messages).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1356#issuecomment-747991302", "url": "https://github.com/xrootd/xrootd/issues/1356#issuecomment-747991302", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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