Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Dr. Carsten Bormann" To: "C. R. Oldham" , Subject: RE: ^C stops ssh with "Killed by signal 2" Date: Fri, 29 Mar 2002 22:17:26 +0100 Message-ID: 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: 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/