And what about attached one ? It seems to do the same
but is less intrusive. htb_debug_dump is meant to do
its output in all cases because it is called from
bug-reporting places too.
But yes the call in htb_dump is superfluous so I used
your idea but changed it a bit. I'll submit it for
inclusion l
No, the patch dose not affect tc only dmesg/klogd ect. It changes printk's into
HTB_DBG macros,
these macros don't print unless you set HTB into debug mode :)
The default kernel workes ?great? with my script 2.4.x and 2.5.x.
Here is an example...
The script workes like so... (10: is the qdisc-i
Sorry Mike,
This isn't an answer to your queries but instead a question. I would
like to know if there are any added fields to the tc -s -d output post
application of the 2.5 kernel patch you have applied below.
Cause i am using htb with 2.4.21 and there isn't much of graphing i can
do with the
I use MRTG to graph tc -d output, so the debug_dump fills up my dmesg logs ect. It's
just
annoying.
Attached is a patch vs 2.5.74 and my MRTG script.
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
linux-2.5.74.htbdebug.patch
D
