Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dr. Carsten Bormann" <cabo AT tzi DOT org>
To: "C. R. Oldham" <cro AT ncacasi DOT org>, <cygwin AT cygwin DOT com>
Subject: RE: ^C stops ssh with "Killed by signal 2"
Date: Fri, 29 Mar 2002 22:17:26 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGGEPIHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-Reply-To: <F540EC7334CFED478994B370191C960914237F@exchange01.ncacasi.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal

> 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/