Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Jaakko Niemi <liiwi@iki.fi>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] commands to see Entire Configuration
Date: Mon, 28 Jan 2002 17:03:03 +0000	[thread overview]
Message-ID: <marc-lartc-101223745326071@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101223284209179@msgid-missing>

rajesh revuru <rvr_kumar@yahoo.com> writes:

> Hi all,
> 
> This may sound strange, but i have a question..
> 
> is there any commands which we can use to see the entire TC configurations..

 tc qdisc show dev eth0
 tc class show dev eth0

 You can add couple command line options to those so that they 
show more information, but you'll have to find them from the tc
manpage :)

                -j
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  reply	other threads:[~2002-01-28 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 15:46 [LARTC] commands to see Entire Configuration rajesh revuru
2002-01-28 17:03 ` Jaakko Niemi [this message]
2002-01-28 18:34 ` rajesh revuru
2002-01-28 18:45 ` Stef Coene
2002-01-28 19:07 ` Jaakko Niemi

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-101223745326071@msgid-missing \
    --to=liiwi@iki.fi \
    --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