From: Andreas Krey <a.krey@gmx.de>
To: Ralph Seichter <git-ml@seichter.de>
Cc: "Carlos Martín Nieto" <cmn@elego.de>, git@vger.kernel.org
Subject: Re: How to limit bandwidth used by git over SSH ?
Date: Wed, 20 Jul 2011 22:20:26 +0200 [thread overview]
Message-ID: <20110720202026.GA30927@inner.h.iocl.org> (raw)
In-Reply-To: <4E272A20.8080904@seichter.de>
On Wed, 20 Jul 2011 21:18:56 +0000, Ralph Seichter wrote:
...
> The general idea to use a tool besides git or SSH to shape the bandwidth
> usage seems valid, though.
There are ways to integrate such a tool easier than the way trickle
does; by using the 'ProxyCommand' configuration option of ssh, like
'ProxyCommand netcat $yourhost 22' or similar. Unfortunately, I don't
know a suitable program offhand, netcat does not seem to have a bandwidth
limiting option. But then such a beast is relatively easy to write.
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
prev parent reply other threads:[~2011-07-20 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:22 How to limit bandwidth used by git over SSH ? Ralph Seichter
2011-07-19 8:42 ` Carlos Martín Nieto
2011-07-20 19:18 ` Ralph Seichter
2011-07-20 20:20 ` Andreas Krey [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110720202026.GA30927@inner.h.iocl.org \
--to=a.krey@gmx.de \
--cc=cmn@elego.de \
--cc=git-ml@seichter.de \
--cc=git@vger.kernel.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 NNTP newsgroup(s).