| 1 |
On Fri, Oct 20, 2006 at 07:09:16PM +0100, Penguin Lover Jorge Almeida squawked: |
| 2 |
> I'm having a problem when composing mail in a ssh session since I |
| 3 |
> upgraded the remote kernel to 2.6.17-gentoo-r8 (I had 2.6.17-gentoo-r7 |
| 4 |
> before). I'm using vim to compose a message in pine and suddenly it stops |
| 5 |
> responding (nothing happens, whatever key I press). I have to kill the |
| 6 |
> session (by killing the window). On the other hand, if I use the embedded |
| 7 |
> pico to compose, there's no problem. Moreover, I had several ssh sessions |
| 8 |
> active, and they responded as usual, so it's not as the connection went |
| 9 |
> down... |
| 10 |
> |
| 11 |
> I always compose messages this way and never had this kind of problem. It |
| 12 |
> happened twice since yesterday, when I upgraded the kernel (can figure out |
| 13 |
> what else can be...). The local kernel is the same (and it was upgraded |
| 14 |
> some time ago). |
| 15 |
> |
| 16 |
> Is there something I can do to try to find the culprit? (Using pico is a |
| 17 |
> real pain, I'm already tired after writing this message!) |
| 18 |
|
| 19 |
Do you have physical access to the remote machine? If you do, try and |
| 20 |
see if you can reproduce it locally at the remote machine, just to |
| 21 |
rule out ssh being the culprit. (Or perhaps you can try running pine |
| 22 |
in a screen session. If ssh is alive, and vim is AWOL, you should be |
| 23 |
able to C-a C-d and detach the screen session.) |
| 24 |
|
| 25 |
Did you upgrade vim? or Pine? What versions of those are you running? |
| 26 |
|
| 27 |
If you suspect the kernel is the problem, is there anything in the |
| 28 |
logs? (dmesg or otherwise). |
| 29 |
|
| 30 |
W |
| 31 |
-- |
| 32 |
I found my "inner child" ... and put the brat up for adoption. |
| 33 |
Sortir en Pantoufles: up 56 days, 12:48 |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives