| 1 |
On 05/25/2011 07:08 AM, Todd Goodman wrote: |
| 2 |
> * Andy Wilkinson <drukargin@×××××.com> [110524 18:02]: |
| 3 |
>> On 05/24/2011 12:38 PM, Todd Goodman wrote: |
| 4 |
>>> * Andy Wilkinson<drukargin@×××××.com> [110524 12:24]: |
| 5 |
>>>> I can't say for sure when this started, as I have gone a while without |
| 6 |
>>>> accessing my computer remotely much, but perhaps since my last upgrade |
| 7 |
>>>> (which may have included openrc), ctrl-c doesn't work over ssh. I have |
| 8 |
>>>> tested this from multiple workstations and even my droid, using |
| 9 |
>>>> different terminal emulators, and have got consistent results. |
| 10 |
>>>> |
| 11 |
>>>> I'm not even sure where to start looking. Googling didn't find me much |
| 12 |
>>>> (at least, not much that's current at all; 5 year-old ubuntu bugs aren't |
| 13 |
>>>> very useful), and I'm not sure at all what might be causing this. Could |
| 14 |
>>>> anyone here point me to something that might be causing this? |
| 15 |
>>>> |
| 16 |
>>>> Thanks, |
| 17 |
>>>> |
| 18 |
>>>> -Andy |
| 19 |
>>> I don't have any problems. What does 'stty -a' show for the intr= bit? |
| 20 |
>>> |
| 21 |
>>> Todd |
| 22 |
>>> |
| 23 |
>> $ stty -a |
| 24 |
>> speed 38400 baud; rows 23; columns 80; line = 0; |
| 25 |
>> intr = ^C; ... |
| 26 |
>> |
| 27 |
>> Which looks right, but when I try to use Ctrl-C, this happens: |
| 28 |
>> |
| 29 |
>> $ ping localhost |
| 30 |
>> PING localhost (127.0.0.1) 56(84) bytes of data. |
| 31 |
>> 64 bytes from localhost (127.0.0.1): icmp_req=1 ttl=64 time=0.037 ms |
| 32 |
>> ^C64 bytes from localhost (127.0.0.1): icmp_req=2 ttl=64 time=0.032 ms |
| 33 |
>> ^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=3 ttl=64 time=0.032 ms |
| 34 |
>> ^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=4 ttl=64 |
| 35 |
>> time=0.034 ms |
| 36 |
>> ^C^C^C^C^C^C64 bytes from localhost (127.0.0.1): icmp_req=5 ttl=64 |
| 37 |
>> time=0.032 ms |
| 38 |
>> ^Z |
| 39 |
>> |
| 40 |
>> This does NOT happen locally: from a console or terminal at the machine, |
| 41 |
>> I can interrupt just fine. Ctrl-Z does//work over ssh. |
| 42 |
>> |
| 43 |
>> Thanks, |
| 44 |
>> |
| 45 |
>> -Andy |
| 46 |
> Very strange (as someone else said.) |
| 47 |
> |
| 48 |
> Only thing I can think of is that something in your startup scripts |
| 49 |
> (.profile, .bashrc, etc.) are doing something different between the |
| 50 |
> two logins. |
| 51 |
> |
| 52 |
> I've seen that most often when they do things based on TERM and it's |
| 53 |
> different between a local login and remote. |
| 54 |
> |
| 55 |
> Maybe make sure your startup scripts run with a 'set -x' at the |
| 56 |
> beginning and compare the output? |
| 57 |
> |
| 58 |
> Good luck, |
| 59 |
> |
| 60 |
> Todd |
| 61 |
> |
| 62 |
Well, for no good reason, a reboot once I was back at the machine fixed |
| 63 |
the issue. I'm not sure why; I didn't change anything. I hate not |
| 64 |
knowing why reboots fix things. :( |
| 65 |
|
| 66 |
-Andy |
Archives