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 1QPaM9-0000sy-2D for garchives@archives.gentoo.org; Thu, 26 May 2011 13:12:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 865E41C14C for ; Thu, 26 May 2011 13:12:04 +0000 (UTC) Received: from ns1.bonedaddy.net (ns1.bonedaddy.net [70.91.141.202]) by pigeon.gentoo.org (Postfix) with ESMTP id 13E9A1C0E2 for ; Thu, 26 May 2011 12:41:07 +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 p4QCAvip014627 for ; Thu, 26 May 2011 08:10:57 -0400 Received: (from tgoodman@localhost) by ns1.bonedaddy.net (8.14.5/8.14.5/Submit) id p4QCAvwt014626 for gentoo-user@lists.gentoo.org; Thu, 26 May 2011 08:10:57 -0400 X-Authentication-Warning: ns1.bonedaddy.net: tgoodman set sender to tsg@bonedaddy.net using -f Date: Thu, 26 May 2011 08:10:57 -0400 From: Todd Goodman To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Ctrl+C not working over ssh? Message-ID: <20110526121057.GD20163@ns1.bonedaddy.net> References: <4DDBE1A5.6000104@gmail.com> <20110524193800.GU20163@ns1.bonedaddy.net> <4DDC3130.5020209@gmail.com> <20110525140807.GZ20163@ns1.bonedaddy.net> <4DDDB27F.9010307@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: <4DDDB27F.9010307@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: X-Archives-Hash: 7c0ede199166d0d64a7daea54129406a * Andy Wilkinson [110525 21:27]: [...] > Well, for no good reason, a reboot once I was back at the machine fixed > the issue. I'm not sure why; I didn't change anything. I hate not > knowing why reboots fix things. :( > > -Andy Argh!!! I did see in a google search that someone else had the problem and a reboot fixed it too. If it ever happens again I'd wonder if all new SSH sessions experience the same problem and if so, if restarting the SSH daemon fixes it too. Or if it's some weirdness with the psuedo-tty system. Todd