[Bug 2476] ssh fails to report IO errors on stdin/stdout/stderr

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=2476

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org

--- Comment #1 from Damien Miller <djm at mindrot.org> ---
Created attachment 2719
  --> https://bugzilla.mindrot.org/attachment.cgi?id=2719&action=edit
report channel write errors

It's easy enough to report write errors (see attachment), but I'm not
sure the best way to handle them. Clobbering a process' exit status is
a bit heavy-handed, since not all processes care about all IO errors.

Some protocol extension that allowed signalling errors back to the
client would be nice - it would at least allow the client to report the
problem to the user (rather than it being buried in the server's
syslog), but it would require both client and server to be running
software that supported it.

If there were some way to force a file descriptor error on the client
side then we could make this a bit more transparent...

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.