Steve [Gentoo] wrote:
I use cygwin openssh to connect to my Gentoo server... recently I've
noticed a change in behaviour.
When I press <ctrl>C I'd expect my gentoo shell (zsh) to abort the
current empty statement and wait for another. These days, however, I
see "Killed by signal 2" and then my ssh connection closes. Does anyone
have any idea why this might have started to happen?
Steve
Apparently the signal is being handled by cygwin on the client side (not a gentoo server
problem). Something must have changed in your cygwin evironment. A quick search shows that
this is a common problem:
http://www.google.com/search?hl=en&q=%22Killed+by+signal+2%22+cygwin+ssh. In the first
search result it suggested to "Switch off ForwardX11 in your .ssh/config".
Zac
--
[email protected] mailing list
