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
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	^C stops ssh with "Killed by signal 2"
X-MimeOLE:	Produced By Microsoft Exchange V6.0.4712.0
Date:	Fri, 29 Mar 2002 10:39:06 -0700
Message-ID:	<F540EC7334CFED478994B370191C960914237F@exchange01.ncacasi.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"C. R. Oldham" <cro AT ncacasi DOT org>
To:	<cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g2THkiJ02222

Greetings,

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?

--
C. R. Oldham, Director of Technology
NCA CASI
Arizona State University
cro AT ncacasi DOT org
V:480-965-8703 F:480-965-9423 


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

- Raw text -