This was fixed in patch 1ea97d1 and will appear in release 4.2.0 The bypass for this problem is to either not use the xrd.port directive or if it must be used to steer the xrootd port choice to say:

xrd.port 18761 if exec xrootd


Reply to this email directly or view it on GitHub.



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