Print

Print

Hi Andy,

We'll move very soon to XrootD 5.1.0 so if this is already fixed even better. But for the moment we don't have any production instance running with XRootD 5 so I can not draw any comparison. Moreover, this does not seem to be a systemic error but triggered only in certain conditions.

Thanks!

—
You are receiving this because you commented.
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/1404#issuecomment-784178835", "url": "https://github.com/xrootd/xrootd/issues/1404#issuecomment-784178835", "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