All of lore.kernel.org
 help / color / mirror / Atom feed
From: <mingching.tiew@redtone.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tools for traffic monitoring
Date: Mon, 27 Jan 2003 01:38:59 +0000	[thread overview]
Message-ID: <marc-lartc-104363176209053@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104317354520400@msgid-missing>


Correct me if I am wrong, your idea of stats collection is based on
iptables. This is beautiful by itself as it is directly related to firewall
rules.
On the other hand, if one's purpose is to measure qdisc/classses,  wouldn't
it be better to use 'tc' , much like those explained in HTB user guide
chapter 7  ?

Examples, tc -s -d qdisc show dev eth0
                tc -s -d class show dev eth0
       etc.

In any case, whether is using tc or iptables, it will require a fork to
collect
results. If I need to run it continuously, any words of advise regarding
avoiding excess load ?

Regards.
----- Original Message -----
From: "Stef Coene" <stef.coene@docum.org>
To: <mingching.tiew@redtone.com>; <lartc@mailman.ds9a.nl>
Sent: Saturday, January 25, 2003 1:37 AM
Subject: Re: [LARTC] tools for traffic monitoring


> I wrote some scripts for long term graphing and a script for real time
> logging.  You can find them all on www.docum.org.  (gui : long term
logging,
> monitorl : real time monitoring).  They work fine for me.
>
> > Appreciate someone could point me where in the '/proc' file system where
> > these data could be gathered.
> There is no tc interface for the /proc interface.
>
> 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/

  parent reply	other threads:[~2003-01-27  1:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 18:23 [LARTC] tools for traffic monitoring Andreas Hasenack
2003-01-21 18:29 ` Meehan, Francois
2003-01-21 18:42 ` Andreas Hasenack
2003-01-21 19:03 ` Morten Isaksen
2003-01-23 11:34 ` Serge Maandag
2003-01-24  1:40 ` mingching.tiew
2003-01-24 17:37 ` Stef Coene
2003-01-25  2:20 ` Ming-Ching Tiew
2003-01-25  9:08 ` Stef Coene
2003-01-27  1:38 ` mingching.tiew [this message]
2003-01-27 18:15 ` Stef Coene

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-104363176209053@msgid-missing \
    --to=mingching.tiew@redtone.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.