* [gentoo-user] Peculiar... ssh / shell glitch...
@ 2005-07-27 17:55 Steve [Gentoo]
2005-07-27 18:48 ` Zac Medico
0 siblings, 1 reply; 3+ messages in thread
From: Steve [Gentoo] @ 2005-07-27 17:55 UTC (permalink / raw
To: gentoo-user
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
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] Peculiar... ssh / shell glitch...
2005-07-27 17:55 [gentoo-user] Peculiar... ssh / shell glitch Steve [Gentoo]
@ 2005-07-27 18:48 ` Zac Medico
2005-07-28 13:44 ` Steve [Gentoo]
0 siblings, 1 reply; 3+ messages in thread
From: Zac Medico @ 2005-07-27 18:48 UTC (permalink / raw
To: gentoo-user
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
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] Peculiar... ssh / shell glitch...
2005-07-27 18:48 ` Zac Medico
@ 2005-07-28 13:44 ` Steve [Gentoo]
0 siblings, 0 replies; 3+ messages in thread
From: Steve [Gentoo] @ 2005-07-28 13:44 UTC (permalink / raw
To: gentoo-user
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=en&q=%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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-07-28 13:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-27 17:55 [gentoo-user] Peculiar... ssh / shell glitch Steve [Gentoo]
2005-07-27 18:48 ` Zac Medico
2005-07-28 13:44 ` Steve [Gentoo]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox