From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] controlling the tc system
Date: Thu, 30 Jan 2003 20:19:20 +0000 [thread overview]
Message-ID: <marc-lartc-104395822804849@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104389725529542@msgid-missing>
On Thursday 30 January 2003 04:26, Jody Belka wrote:
> hi,
>
> i've been trying to find some information on this but haven't had any
> luck. what i'm interested in is any way to control the tc system
> progmatically without having to shell out to the tc program. i've already
> found some stuff for controlling iptables progmatically, but have been out
> of luck so far with traffic control. does anyone have any ideas?
http://tcng.sourceforge.net/
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-30 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 3:26 [LARTC] controlling the tc system Jody Belka
2003-01-30 20:19 ` Stef Coene [this message]
2003-01-31 3:46 ` Don Gould
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=marc-lartc-104395822804849@msgid-missing \
--to=stef.coene@docum.org \
--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