Print

Print

One more thing, EEXISTS is now mapped to kXR_InvalidRequest which is used to indicate what is meant (e.g. duplicate logins, bypassing authentication, bad request code). So, dumping EEXISTS in that mess is awkward but not devastating. I suppose you'd want a separate error code for that when we fix this in R5, right?

—
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/1167#issuecomment-605516325", "url": "https://github.com/xrootd/xrootd/issues/1167#issuecomment-605516325", "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