From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org, Thomas Graf <tgraf@suug.ch>
Subject: Re: [IPROUTE]: Introduce tc monitor
Date: Mon, 03 Jul 2006 12:13:53 +0200 [thread overview]
Message-ID: <44A8EDE1.7030503@trash.net> (raw)
In-Reply-To: <1151860849.5093.259.camel@jzny2>
jamal wrote:
> Speaking of events reminded me of this.. Managed to get some quality
> time, so heres a patch against current iproute2 git that adds something
> useful.
>
> This patch adds ability to monitor tc events similar to ipmonitor.
> User runs "tc monitor" (without quotes) and watches events of
> addition, deletion and updates from qdiscs, classes, filters and
> actions as they happen.
Looks good to me. Speaking of actions, do you have any plans to
add help-texts? Currently the output is very confusing, whenever
I use them I need to google for examples.
$ tc action help
action usage improper
$ tc action add mirred help
mirred not supported help
bad action parsing
parse_action: bad value (2:mirred)!
Illegal "action"
Command "add" is unknown, try "tc action help".
next prev parent reply other threads:[~2006-07-03 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 17:20 [IPROUTE]: Introduce tc monitor jamal
2006-07-03 10:13 ` Patrick McHardy [this message]
2006-07-04 13:15 ` jamal
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=44A8EDE1.7030503@trash.net \
--to=kaber@trash.net \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=tgraf@suug.ch \
/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).