All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] graphics? we don't need no stinkin graphics!
Date: Tue, 16 Dec 2003 21:48:44 +0000	[thread overview]
Message-ID: <marc-lartc-107161327414668@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107123980923219@msgid-missing>

On Monday 15 December 2003 20:29, Stef Coene wrote:
> On Monday 15 December 2003 10:45, raptor wrote:
> > |> still tempted to extend using rrdtool, u know what they say "a picture
> > |> is like a thousand words"
> > |
> > |Like http://home.docum.org/rrd-test.html ?
> > |
> > |Stef
> >
> > ]- could u share this tcc-rrd script :")
>
> Check http://docum.org/stef.coene/qos/tc-snmp/ in a couple of days.
> I'm rewriting the extension and my scripts to include parent - child
> relation information.
For those who are interested in the snmp extension, I created some scripts (2) 
to graph the information :
http://docum.org/stef.coene/qos/tc-snmp/

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

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

  parent reply	other threads:[~2003-12-16 21:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 14:34 [LARTC] graphics? we don't need no stinkin graphics! Chijioke Kalu
2003-12-12 14:42 ` Chijioke Kalu
2003-12-12 14:48 ` Stef Coene
2003-12-12 15:05 ` Toby Cantor
2003-12-12 15:31 ` Chijioke Kalu
2003-12-12 16:42 ` Stef Coene
2003-12-15  9:45 ` raptor
2003-12-15 19:29 ` Stef Coene
2003-12-16 21:48 ` Stef Coene [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-12  8:46 Toby Cantor
2003-12-15 12:51 ` raptor

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-107161327414668@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 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.