| 1 |
Steve [Gentoo] wrote: |
| 2 |
> I use cygwin openssh to connect to my Gentoo server... recently I've |
| 3 |
> noticed a change in behaviour. |
| 4 |
> |
| 5 |
> When I press <ctrl>C I'd expect my gentoo shell (zsh) to abort the |
| 6 |
> current empty statement and wait for another. These days, however, I |
| 7 |
> see "Killed by signal 2" and then my ssh connection closes. Does anyone |
| 8 |
> have any idea why this might have started to happen? |
| 9 |
> |
| 10 |
> Steve |
| 11 |
> |
| 12 |
> |
| 13 |
|
| 14 |
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". |
| 15 |
|
| 16 |
Zac |
| 17 |
-- |
| 18 |
gentoo-user@g.o mailing list |
Archives