> > server.c:
> > - The most painful change is that if we have a PTY we _must_ pipe the stderr
> > through the PTY! If we don't do this, programs which want to set the
> > terminal params, will fail with a message like this: "stderr: invalid
> > argument". And also bash will look bad, because the prompt is printed to the
> > stderr, and if it goes through a separate channel, the client will display
> > it incorrectly on its raw terminal.
>
> I must say that I *really* don't like this change. I want to be able,
> for instance, to run an interactive program on the server, while
> redirecting stderr to a local log file. And the ssh2 protocol lets me
> do things like that.
ssh2 protocol allows this, but the reference implementation
(datafelows') doesn't use stderr either. the only solution that may work
is to allocate two pseudo-ttys one for stdout and the other for stderr,
but I am not sure it would work (since programs which set termios modes on
the remote side, set it on only one of the output fds)
I think most interactive programs assume that stdout=stderr and both of
them refer to the same tty.
--- Bazsi
