Re: ssh ControlMaster problem, workaround

On 2008-07-19 18:23:32 -0500, Peter Samuelson wrote:
> [Stefan Sperling]
> > Another idea:
> > Couldn't we redirect stderr of the ssh process to somewhere else
> > then the screen before we kill it?
>
> Well, ssh could print many things to stderr, including other connection
> errors, or password prompts, or errors forwarded from the other end of
> the tunnel. I don't think we want to suppress those.

Stefan said: "before we kill it". So, there should be no useful at
that time. At least, I think you won't lose more information than
with a kill -9.

> (And you can't redirect the child's stderr after you exec("ssh").)

Good point. You can still redirect the child's stderr before the exec,
send the data where it need be and discard stderr after the kill. I'm
not sure this is a good idea, though (side effects? possible buffering
problems? possible synchronization problems? [*]).

[*] I tried to write a utility that does stderr coloring at the shell
level and there had been many problems in practice. I eventually
abandoned the idea.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org