From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Incoming traffic?
Date: Tue, 04 Oct 2005 17:53:16 +0000 [thread overview]
Message-ID: <4342C18C.9010205@gmx.net> (raw)
In-Reply-To: <op.sx37hpsigft90w@dominik.test>
Dominik Werder schrieb:
> Hi there,
>
> a program is downloading large files on a regular basis and has no
> switch to limit bandwidth.
>
> Is there a way to shape this incoming traffic? Any pointers?
Use trickle.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-04 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 9:33 [LARTC] Incoming traffic? Dominik Werder
2005-10-04 10:00 ` Andreas Klauer
2005-10-04 13:08 ` Edward Smith
2005-10-04 17:53 ` Carl-Daniel Hailfinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-10 16:15 [LARTC] incoming traffic?? sun reflex4
2003-05-10 18:05 ` Jose Luis Domingo Lopez
2003-05-11 4:49 ` hare ram
2003-05-11 10:13 ` sun reflex4
2003-05-11 12:37 ` Graste
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=4342C18C.9010205@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=lartc@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