^C stops ssh with "Killed by signal 2"

[Dr. Carsten Bormann]

> Does anyone know why hitting ^C within an ssh session kills ssh instead
> of passing the ^C on to the host?  I get
>
> Killed by signal 2
>
> Every time.  It hasn't always done this.  Is there a setting somewhere I
> can tweak?

Switch off ForwardX11 in your .ssh/config

No, I don't know why this helps either, but this was discussed in the
mailing list previously.
It's been this way for a while...

Gruesse, Carsten


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/