All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Charvat <michal@lounsko.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Graphing tc output
Date: Thu, 11 Dec 2003 12:57:58 +0000	[thread overview]
Message-ID: <marc-lartc-107114755124473@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107107433516257@msgid-missing>

Hi,

Sorry for that, but yet another update :-)

Originally I compiled code on RH8.0, now I tried on Debian stable,
and I had to make some changes (looks like older gcc didn't like
my code :-( ).

http://x-ray.prokon.cz/data/snmp-12-11-2003.tgz

Michal Charvat
Prokon R.B.S. Louny v.o.s.


On Thu, 11 Dec 2003, Cezar Atanasiu wrote:

>
>  me too :)
>
> On Wed, 10 Dec 2003 22:35:29 +0100 (CET)
> Michal Charvat <michal@lounsko.cz> wrote:
>
> > Ok, I've put my code to: http://x-ray.prokon.cz/data/snmp.tgz
> >
> > It's quite simple, some code is copied from tc utility source...
> > follow instructions in package and it should work...
> >
> > Michal Charvat
> > Prokon R.B.S. Louny v.o.s.
> >
> >
> > On Wed, 10 Dec 2003, Damjan wrote:
> >
> > > > I've recently written snmp extension to Net-SNMP package
> > > > (www.net-snmp.net), where it's possible to get kernel statistics
> > > > directly via snmp requests.
> > > >
> > > > But it's still beta quality :-( (known one memory leak, I'm going
> > > > to look at it tommorow)
> > > >
> > > > If you are interested, I can put it somewhere...
> > >
> > > Sure everybody is interested :)
> > >
> > > put it somewhere, maybe someone will find that memory leak before
> > > you do :)
> > >
> > >
> > > --
> > > Damjan Georgievski
> > > jabberID: damjan@bagra.net.mk
> > > _______________________________________________
> > > LARTC mailing list / LARTC@mailman.ds9a.nl
> > > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
> > > http://lartc.org/
> > >
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
>
>
>
>
> --
> Cezar ATANASIU
> GMB Computers
> Departamentul Internet
> Tel/fax: +40 241 619222/673199
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-12-11 12:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 16:39 [LARTC] Graphing tc output Rajkumar S
2003-12-10 18:53 ` Chijioke Kalu
2003-12-10 18:54 ` Michal Charvat
2003-12-10 19:58 ` Damjan
2003-12-10 21:35 ` Michal Charvat
2003-12-11 11:16 ` Stef Coene
2003-12-11 12:05 ` Cezar Atanasiu
2003-12-11 12:57 ` Michal Charvat [this message]
2003-12-11 12:59 ` Kristiadi Himawan
2003-12-11 13:16 ` Michal Charvat
2003-12-11 13:23 ` Stef Coene
2003-12-11 14:58 ` Stef Coene
2003-12-11 15:19 ` Michal Charvat
2003-12-11 16:15 ` Stef Coene
2003-12-11 16:27 ` Michal Charvat
2003-12-11 16:49 ` 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-107114755124473@msgid-missing \
    --to=michal@lounsko.cz \
    --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.