| 1 |
On 05/24/2011 12:38 PM, Todd Goodman wrote: |
| 2 |
> * Andy Wilkinson<drukargin@×××××.com> [110524 12:24]: |
| 3 |
>> I can't say for sure when this started, as I have gone a while without |
| 4 |
>> accessing my computer remotely much, but perhaps since my last upgrade |
| 5 |
>> (which may have included openrc), ctrl-c doesn't work over ssh. I have |
| 6 |
>> tested this from multiple workstations and even my droid, using |
| 7 |
>> different terminal emulators, and have got consistent results. |
| 8 |
>> |
| 9 |
>> I'm not even sure where to start looking. Googling didn't find me much |
| 10 |
>> (at least, not much that's current at all; 5 year-old ubuntu bugs aren't |
| 11 |
>> very useful), and I'm not sure at all what might be causing this. Could |
| 12 |
>> anyone here point me to something that might be causing this? |
| 13 |
>> |
| 14 |
>> Thanks, |
| 15 |
>> |
| 16 |
>> -Andy |
| 17 |
> I don't have any problems. What does 'stty -a' show for the intr= bit? |
| 18 |
> |
| 19 |
> Todd |
| 20 |
> |
| 21 |
$ stty -a |
| 22 |
speed 38400 baud; rows 23; columns 80; line = 0; |
| 23 |
intr = ^C; ... |
| 24 |
|
| 25 |
Which looks right, but when I try to use Ctrl-C, this happens: |
| 26 |
|
| 27 |
$ ping localhost |
| 28 |
PING localhost (127.0.0.1) 56(84) bytes of data. |
| 29 |
64 bytes from localhost (127.0.0.1): icmp_req=1 ttl=64 time=0.037 ms |
| 30 |
^C64 bytes from localhost (127.0.0.1): icmp_req=2 ttl=64 time=0.032 ms |
| 31 |
^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=3 ttl=64 time=0.032 ms |
| 32 |
^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=4 ttl=64 |
| 33 |
time=0.034 ms |
| 34 |
^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=5 ttl=64 |
| 35 |
time=0.032 ms |
| 36 |
^Z |
| 37 |
|
| 38 |
This does NOT happen locally: from a console or terminal at the machine, |
| 39 |
I can interrupt just fine. Ctrl-Z does//work over ssh. |
| 40 |
|
| 41 |
Thanks, |
| 42 |
|
| 43 |
-Andy |
Archives