[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Killing a hung ssh process in a TRAMP session
From: |
Suvayu Ali |
Subject: |
Re: Killing a hung ssh process in a TRAMP session |
Date: |
Sun, 17 Jan 2010 11:18:48 -0800 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-3.fc11 Lightning/1.0pre Thunderbird/3.0 |
Hi Michael,
On Sunday 17 January 2010 04:23 AM, Michael Albinus wrote:
Suvayu Ali<fatkasuvayu+linux@gmail.com> writes:
These are the steps I took to generate the backtrace, after setting
the variables as you requested.
I could reproduce it. Unfortunately, there is no simple way to solve it
inside Tramp (but I will continue to investigate). Therefore, I have
added the following item to Tramp's Frequently Asked Questions, HTH:
Thank you so much for clarifying this issue. :)
* TRAMP does not recognize hung `ssh' sessions
When your network connection is down, `ssh' sessions might hang.
TRAMP cannot detect it safely, because it still sees a running
`ssh' process. Timeouts cannot be used as well, because it
cannot be predicted, how long a remote command will last, for
example when copying very large files.
Therefore, you must configure the `ssh' process to die in such a
case. The following entry in `~/.ssh/config' would do the job:
Host *
ServerAliveInterval 5
I was thinking something along similar lines, good to see I was on the
correct track. :)
Best regards, Michael.
Cheers,
--
Suvayu
Open source is the future. It sets us free.