How should I handle EINTR from syscall.Dup2 (Linux)?
- The effect of SA_RESTART on dup2(2) is undocumented.
- If dup2 returns EINTR, can I be sure that nothing has been done? (Otherwise
retrying is racy.)
- libuv uv__dup2_cloexec [1] never retries the syscall but treats EINTR as a
failure.
- Python os.dup2 [2] also never retries, but it seems that it treats EINTR as
success ("ignores EINTR error").
- See also unresolved question:
https://stackoverflow.com/questions/15930013/can-dup2-really-return-eintr
All very confusing.
Also, can os.File.Close / syscall.Close return EINTR? Is it affected by
SA_RESTART?
[1] https://github.com/libuv/libuv/issues/462
[2] https://www.python.org/dev/peps/pep-0475
--
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/9c8cc343-48f0-4f14-9e32-9b14647bacd0%40googlegroups.com.
