Niels M�ller wrote:
>
> Keresztfalvi Gabor <[EMAIL PROTECTED]> writes:
> > 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.
stderr _must_ be processed the same way stdin is. If you don't want them
to share a pty, you need to allocate 2 (which is what the kerberos stuff
does, as I recall).
--
Carson Gaspar
[EMAIL PROTECTED]
