From: Matthew Kennedy <mkennedy@gentoo.org>
Subject: implementing a heartbeat for tramp
Date: Thu, 23 Oct 2003 21:57:14 GMT [thread overview]
Message-ID: <877k2vpqjz.fsf@killr.ath.cx> (raw)
A router I have to work through frequently seems to kill inactive ssh
sessions after a few minutes for no apparent reason. If I'm using
tramp with one of the ssh or scp methods, then this means my tramp
connection is killed, causing tramp to reconnect automatically and go
though its time-consuming initialization phase.
Based on my very effective hack where I run "xclock -update 10" to
cause some activity on the connection every 10 seconds during remote
shell sessions, I thought I might attempt something similar with
tramp... call it a "tramp heart-beat" if you will.
My idea was to create a timer, which walked all emacs buffers looking
for tramp buffers. When it found one, it would (maybe)
`tramp-send-command' to send a heart-beat (I guess some kind of null
operation... touch /dev/null??? -- or maybe the command itself
suffices)
Does this sound reasonable? Any other ways to approach this problem
perhaps?
Matt
--
Matthew Kennedy
next reply other threads:[~2003-10-23 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 21:57 Matthew Kennedy [this message]
2003-10-24 3:20 ` implementing a heartbeat for tramp Dan Anderson
2003-10-30 21:22 ` Kai Grossjohann
2003-11-01 3:03 ` Matthew Kennedy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877k2vpqjz.fsf@killr.ath.cx \
--to=mkennedy@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).