X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<499C49A6.7000700@gmail.com>
Date:	Thu, 19 Feb 2009 01:47:18 +0800
From:	Chan Kar Heng <chankarheng AT gmail DOT com>
User-Agent:	Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Revisiting "Killed by signal 2" caused by ssh -X.
References:	<49961E96 DOT 8080909 AT veritech DOT com> <20090214095952 DOT GX5416 AT calimero DOT vinschen DOT de> <d508790c0902141035g5017703fy556cc168553abb85 AT mail DOT gmail DOT com>
In-Reply-To:	<d508790c0902141035g5017703fy556cc168553abb85@mail.gmail.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Hi all.

I'm consistently getting "Killed by signal 2" when I press ctrl-c in an 
ssh -X session. I've searched the forums & it seems there hasn't been a 
solution for this?

Is there a way to prevent getting "Killed by signal 2" when I press 
ctrl-c in ssh -X sessions?

For now, what I do is this:
- Before running ssh -X, in the current cygwin shell, I do a 'trap "" 
2'. That's so that the current cygwin shell will ignore sigint.
- Once that's done, I proceed with ssh -X. Cause of the previous step, 
Ctrl-C is now completely ignored.
- I then paste `awk 'BEGIN{printf("stty intr %c\n",29)}' /dev/null` into 
the shell prompt to set ctrl-] as stty intr.

Hope my temporary solution is useful to those who couldn't get this 
fixed yet.

Thanks!

KarHeng

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -