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 1QP0ac-00010W-SY for garchives@archives.gentoo.org; Tue, 24 May 2011 23:00:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F24F21C01C; Tue, 24 May 2011 22:59:10 +0000 (UTC) Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id C3D231C01C for ; Tue, 24 May 2011 22:59:10 +0000 (UTC) Received: by vws13 with SMTP id 13so6632449vws.40 for ; Tue, 24 May 2011 15:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; bh=eC1K5oe4Aq9c0heh48f5Nm5GZ3cBCKzFqQi4/K7+9Pk=; b=gbtFY1UbTi3Gcdzm2TI3okcqdFhx+A8FCnN2DI/DBkg6Y+q3m9+keFK9Zfykf6q4w1 b3jlLJ/kzfOCpDGiLqHjviIEzyoMS6HZS4jfsohTzTlfOzJ4Uvrvfn14aPS3U5UgFuAY ls6Ov2aEXxaHmtgAa2f05UZmzAeLvyP7HrWyI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=Gyz6OvznQcIGkRxW3jkgQcqT90xoz2rvrF6WvGfx5shoArX39VZHJD/SwgFpJ1uSn2 3IBc8NnsJFEkT9XHxmkKX7UrZjiItLJggwFKEw3rhNROnv63zLQjA3vBOw3uoUjHJ3gJ PuTucQQT9MBl1XNrxGcfRauLoWq0c21C1KOV8= Received: by 10.52.180.201 with SMTP id dq9mr6117185vdc.245.1306277950167; Tue, 24 May 2011 15:59:10 -0700 (PDT) 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 Sender: paul.hartman@gmail.com Received: by 10.52.157.234 with HTTP; Tue, 24 May 2011 15:58:49 -0700 (PDT) In-Reply-To: <4DDC3130.5020209@gmail.com> References: <4DDBE1A5.6000104@gmail.com> <20110524193800.GU20163@ns1.bonedaddy.net> <4DDC3130.5020209@gmail.com> From: Paul Hartman Date: Tue, 24 May 2011 17:58:49 -0500 X-Google-Sender-Auth: 8zn9UZJfp9oj-xllla2PrZ4vu4k Message-ID: Subject: Re: [gentoo-user] Ctrl+C not working over ssh? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 18c327ccddd4cd994d70e55461e0c377 On Tue, May 24, 2011 at 5:29 PM, Andy Wilkinson wrote= : > On 05/24/2011 12:38 PM, Todd Goodman wrote: >> >> * Andy Wilkinson =A0[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. =A0I ha= ve >>> 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. =A0Googling didn't find me mu= ch >>> (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. =A0Co= uld >>> anyone here point me to something that might be causing this? >>> >>> Thanks, >>> >>> -Andy >> >> I don't have any problems. =A0What does 'stty -a' show for the intr=3D b= it? >> >> Todd >> > $ stty -a > speed 38400 baud; rows 23; columns 80; line =3D 0; > intr =3D ^C; ... > > Which looks right, but when I try to use Ctrl-C, this happens: > > $ ping localhost > PING localhost (127.0.0.1) 56(84) bytes of data. > 64 bytes from localhost (127.0.0.1): icmp_req=3D1 ttl=3D64 time=3D0.037 m= s > ^C64 bytes from localhost (127.0.0.1): icmp_req=3D2 ttl=3D64 time=3D0.032= ms > ^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=3D3 ttl=3D64 time=3D0= .032 ms > ^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=3D4 ttl=3D64 > time=3D0.034 ms > ^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=3D5 ttl=3D64 > time=3D0.032 ms > ^Z > > This does NOT happen locally: from a console or terminal at the machine, = I > can interrupt just fine. =A0Ctrl-Z does//work over ssh. That's so strange... I'm curious, if you open another terminal and issue SIGINT to that process (using kill), does it work? I think it should be the equivalent to hitting ctrl-c interactively. "trap" command can be used in scripts to block certain signals... I wonder if your profile/bashrc/or something has a trap entry. But if that's the case I would guess that the same problem would happen locally, and not only remotely (unless remote session uses a different shell or something). Just a W.A.G. :)