1 |
On Tue, May 24, 2011 at 5:29 PM, Andy Wilkinson <drukargin@×××××.com> wrote: |
2 |
> On 05/24/2011 12:38 PM, Todd Goodman wrote: |
3 |
>> |
4 |
>> * Andy Wilkinson<drukargin@×××××.com> [110524 12:24]: |
5 |
>>> |
6 |
>>> I can't say for sure when this started, as I have gone a while without |
7 |
>>> accessing my computer remotely much, but perhaps since my last upgrade |
8 |
>>> (which may have included openrc), ctrl-c doesn't work over ssh. I have |
9 |
>>> tested this from multiple workstations and even my droid, using |
10 |
>>> different terminal emulators, and have got consistent results. |
11 |
>>> |
12 |
>>> I'm not even sure where to start looking. Googling didn't find me much |
13 |
>>> (at least, not much that's current at all; 5 year-old ubuntu bugs aren't |
14 |
>>> very useful), and I'm not sure at all what might be causing this. Could |
15 |
>>> anyone here point me to something that might be causing this? |
16 |
>>> |
17 |
>>> Thanks, |
18 |
>>> |
19 |
>>> -Andy |
20 |
>> |
21 |
>> I don't have any problems. What does 'stty -a' show for the intr= bit? |
22 |
>> |
23 |
>> Todd |
24 |
>> |
25 |
> $ stty -a |
26 |
> speed 38400 baud; rows 23; columns 80; line = 0; |
27 |
> intr = ^C; ... |
28 |
> |
29 |
> Which looks right, but when I try to use Ctrl-C, this happens: |
30 |
> |
31 |
> $ ping localhost |
32 |
> PING localhost (127.0.0.1) 56(84) bytes of data. |
33 |
> 64 bytes from localhost (127.0.0.1): icmp_req=1 ttl=64 time=0.037 ms |
34 |
> ^C64 bytes from localhost (127.0.0.1): icmp_req=2 ttl=64 time=0.032 ms |
35 |
> ^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=3 ttl=64 time=0.032 ms |
36 |
> ^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=4 ttl=64 |
37 |
> time=0.034 ms |
38 |
> ^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=5 ttl=64 |
39 |
> time=0.032 ms |
40 |
> ^Z |
41 |
> |
42 |
> This does NOT happen locally: from a console or terminal at the machine, I |
43 |
> can interrupt just fine. Ctrl-Z does//work over ssh. |
44 |
|
45 |
That's so strange... |
46 |
|
47 |
I'm curious, if you open another terminal and issue SIGINT to that |
48 |
process (using kill), does it work? I think it should be the |
49 |
equivalent to hitting ctrl-c interactively. |
50 |
|
51 |
"trap" command can be used in scripts to block certain signals... I |
52 |
wonder if your profile/bashrc/or something has a trap entry. But if |
53 |
that's the case I would guess that the same problem would happen |
54 |
locally, and not only remotely (unless remote session uses a different |
55 |
shell or something). Just a W.A.G. :) |