On Sat, Feb 29, 2020 at 7:35 AM Uli Kunitz <uli.kun...@gmail.com> wrote:
> My reading of the Linux kernel sources (5.3) is that dup2 will never > return -EINTR. Any necessary file closure will happen, but its return value > will be ignored. > That a specific implementation might never return EINTR as a result of a `dup2()` call is irrelevant. The question is what happens on any UNIX like system. It is also not at all clear that even Linux won't return EINTR given the vagaries of complex API layering. Your statement that "Any necessary file closure will happen" is unfounded. The whole point of returning EINTR is that the close did not happen. If the close was successful then there was no point in returning an EINTR failure. -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CABx2%3DD8E6wMJpfwF4sP_6%2B1-2ELNjtr-TsHAgTUzfmwgqSE4yA%40mail.gmail.com.
