From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB debug info in kernel log
Date: Thu, 13 Feb 2003 07:30:25 +0000 [thread overview]
Message-ID: <marc-lartc-104512150111490@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104511747608833@msgid-missing>
On Thursday 13 February 2003 08:10, Brad Davidson wrote:
> I set up a Perl script to parse the output of 'tc -s qdisc show dev <if>'
> to get stats for MRTG. The only problem is, every time the tc command runs,
> I get many lines output to my kernel level syslog - 84, to be exact They
> look something like this:
>
> oatmail kernel: htb*c10124 m=2 t"748 c\x19272 pq=0 dfI07008 ql=0 pa=0 f:
> oatmail kernel: htb*c10094 m=2 t†150 c†150 pq=0 df#7568 ql=0 pa=0 f:
> oatmail kernel: htb*g j\x171630276
> oatmail kernel: htb*r7 m=0
> oatmail kernel: htb*r6 m=0
>
> I found some reference in the source to a command to tc to set various
> debug levels, although the function that seems to be printing the info
> (htb_debug_dump) does not seem to care about the set level - if debug is
> defined, it prints. Short of altering the DEFINE statement and recompiling
> the kernel, is there any way to disable this output?
I had the same problem. I uncomment the DEFINE statement. But logging there
numbers, means there is something miss with your htb setup and has nothing to
do with you asking for statistics. You can find more info on the homepage of
htb. But it's possible that your rates settings are too low.
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/
next prev parent reply other threads:[~2003-02-13 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 6:24 [LARTC] HTB debug info in kernel log Brad Davidson
2003-02-13 7:30 ` Stef Coene [this message]
2003-02-13 8:48 ` Brad Davidson
2003-02-13 17:37 ` Brad Davidson
2003-02-13 18:35 ` Stef Coene
2003-02-13 23:44 ` Brad Davidson
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-104512150111490@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.