- User Since
- Feb 3 2015, 11:06 PM (248 w, 6 d)
Feb 5 2015
The file is always stdout. We have been unable to determine *definitively* who is setting it non-blocking, but /bin/sh both opens files non-blocking in exec.c and changes the file mode to non-blocking in redir.c, so if I had to guess, it would be stdout redirected to a pipe.
Feb 4 2015
Actually, after reading https://lists.freebsd.org/pipermail/freebsd-bugs/2012-February/047528.html I am starting to wonder if this wouldn't be better addressed at a stdio / write syscall wrapper level. We're also seeing highly intermittent errors with other utilities, like cat(1).