From: Daniel Wittenberg <daniel-wittenberg@starken.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ improvement ideas
Date: Mon, 14 Jan 2002 04:23:33 +0000 [thread overview]
Message-ID: <marc-lartc-101098243130347@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101094979511667@msgid-missing>
really? I didn't see it complaining, and it appeared to be so by the
help if you look at the docs...so what is this really doing, and what is
the del command for? I'm just learning, so I'm only going by what I've
read so far.
*is now confused*
Dan
On Sun, 2002-01-13 at 20:02, John Huttley wrote:
>
>
> > To change, can't you just do:
> > tc del dev eth0 root handle 1:
> >
> > (or whatever your handles are, you get the idea)
> >
> > Shouldn't that essentially "flush" all the shaping under then 1: handle?
>
> This is not a valid command.
>
> The other way is to stop and start networking. Really, I'd just rather
> reboot and be done with it.
>
> Regards
>
> John
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-01-14 4:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 19:21 [LARTC] SFQ improvement ideas devik
2002-01-13 21:06 ` John Huttley
2002-01-13 21:10 ` Daniel Wittenberg
2002-01-14 2:02 ` John Huttley
2002-01-14 4:23 ` Daniel Wittenberg [this message]
2002-01-14 5:13 ` Don Cohen
2002-01-14 9:35 ` Martin Devera
2002-01-14 9:36 ` Martin Devera
2002-01-14 9:38 ` Martin Devera
2002-01-14 9:54 ` Martin Devera
2002-01-14 14:56 ` Michael T. Babcock
2002-01-14 22:33 ` Don Cohen
2002-01-16 9:46 ` Martin Devera
2002-01-16 10:07 ` Martin Devera
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-101098243130347@msgid-missing \
--to=daniel-wittenberg@starken.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.