From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QOxv1-0000FQ-9S for garchives@archives.gentoo.org; Tue, 24 May 2011 20:09:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E73931C005; Tue, 24 May 2011 20:08:08 +0000 (UTC) Received: from ns1.bonedaddy.net (ns1.bonedaddy.net [70.91.141.202]) by pigeon.gentoo.org (Postfix) with ESMTP id AC5A41C005 for ; Tue, 24 May 2011 20:08:08 +0000 (UTC) Received: from ns1.bonedaddy.net (localhost [127.0.0.1]) by ns1.bonedaddy.net (8.14.5/8.14.4) with ESMTP id p4OJc0Tl019616 for ; Tue, 24 May 2011 15:38:00 -0400 Received: (from tgoodman@localhost) by ns1.bonedaddy.net (8.14.5/8.14.5/Submit) id p4OJc0gx019615 for gentoo-user@lists.gentoo.org; Tue, 24 May 2011 15:38:00 -0400 X-Authentication-Warning: ns1.bonedaddy.net: tgoodman set sender to tsg@bonedaddy.net using -f Date: Tue, 24 May 2011 15:38:00 -0400 From: Todd Goodman To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Ctrl+C not working over ssh? Message-ID: <20110524193800.GU20163@ns1.bonedaddy.net> References: <4DDBE1A5.6000104@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DDBE1A5.6000104@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: X-Archives-Hash: ab5e5fc59473ecda8a88198b874d0ead * Andy Wilkinson [110524 12:24]: > I can't say for sure when this started, as I have gone a while without > accessing my computer remotely much, but perhaps since my last upgrade > (which may have included openrc), ctrl-c doesn't work over ssh. I have > tested this from multiple workstations and even my droid, using > different terminal emulators, and have got consistent results. > > I'm not even sure where to start looking. Googling didn't find me much > (at least, not much that's current at all; 5 year-old ubuntu bugs aren't > very useful), and I'm not sure at all what might be causing this. Could > anyone here point me to something that might be causing this? > > Thanks, > > -Andy I don't have any problems. What does 'stty -a' show for the intr= bit? Todd