I left a comment in the pull request but I will post here as well.

I looked, indeed, the cmsd does not differentiate the between ENOENT and EEXISTS.
That can be fixed. I don't particularly like relying on message text as that tends
to change over time as people complain that the message isn't sufficiently
descriptive.

The correct error code should have been returned by the cmsd and, in fact, it's supposed to do that. I agree that it isn't obvious because error code handling becomes complicated when the cmsd attempts a retry and gets yet another error. However, in this case it's pretty straightforward as a retry is not possible. So, it's not too complicated to fix this.

That does that change your opinion on the fix?

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