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