bugzilla-daemon at mindrot.org
2002-Aug-22 22:21 UTC
[Bug 26] ssh setting O_NONBLOCK on stderr can upset CVS
http://bugzilla.mindrot.org/show_bug.cgi?id=26 ------- Additional Comments From markus at openbsd.org 2002-08-23 08:21 ------- hm, what do you suggest? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Aug-23 07:08 UTC
[Bug 26] ssh setting O_NONBLOCK on stderr can upset CVS
http://bugzilla.mindrot.org/show_bug.cgi?id=26 ------- Additional Comments From dhowells at redhat.com 2002-08-23 17:08 ------- I would suggest that SSH shouldn't set O_NONBLOCK on its stderr output. It is only for errors after all, and ssh won't normally be writing to it, and so doing that ought not to be a problem. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Possibly Parallel Threads
- [Bug 26] ssh setting O_NONBLOCK on stderr can upset CVS
- ssh client is setting O_NONBLOCK on a pipe shared with other processes
- ssh client is setting O_NONBLOCK on a pipe shared with other processes
- ssh client is setting O_NONBLOCK on a pipe shared with other processes
- ssh client is setting O_NONBLOCK on a pipe shared with other processes