On Tue May 9 21:20:07 2023 +0000, Paul Gofman wrote:
We'd also need to limit it to connected UDP then which both adds complications, if not an extra server call. But I hope we might rely on the sockets not giving ECONNREFUSED for send() in any other cases, error codes are documented and breaking those in Unix kernel will probably break a lot of things anyway.
I also can imagine that in theory something between the lines of commit 4e6a5d62ad2bbccafa751812ca31eb9ffa25727e may happen (while I am not immediately sure how to trigger that), but in that case calling send() once again won't hurt too probably, even if to get a more sensible error code.