Re: [gentoo-user] Peculiar... ssh / shell glitch...
Zac Medico wrote: 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=enq=%22Killed+by+signal+2%22+cygwin+ssh. In the first search result it suggested to Switch off ForwardX11 in your .ssh/config. Thanks... I guess I suspected gentoo rather than cygwin as I first noticed just after an emerge -uD world... Cygwin it must be then. Steve -- gentoo-user@gentoo.org mailing list
[gentoo-user] Peculiar... ssh / shell glitch...
I use cygwin openssh to connect to my Gentoo server... recently I've noticed a change in behaviour. When I press ctrlC 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 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Peculiar... ssh / shell glitch...
Steve [Gentoo] wrote: I use cygwin openssh to connect to my Gentoo server... recently I've noticed a change in behaviour. When I press ctrlC 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=enq=%22Killed+by+signal+2%22+cygwin+ssh. In the first search result it suggested to Switch off ForwardX11 in your .ssh/config. Zac -- gentoo-user@gentoo.org mailing list
