delete tc entries
I'm a newbie to tc and after some experimenting I have the following problem:
# tc qdisc show qdisc sfq 8006: dev ipsec0 quantum 1514b perturb 15sec
I can't get rid of this entry. Is there a way to clear all entries? I tried all sorts of "tc qdisc del xxx" but nothing seems to work. It says:
RTNETLINK answers: No such file or directory
What syntax do I need to delete this entry?
Richard.
Signature · 13 lines
___________________________________________________________________ The Linux documentation paradox: You have to know the answer before you ask the question +------------------------------------------------------------------+ | Richard Lucassen, Utrecht, Linux 2.4.14 RedHat 7.1 | | The Netherlands i686/1200MHz/512MB | | Public key: http://www.xs4all.nl/~pe1bbf/pubkey.asc | +------------------------------------------------------------------+ _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
Quoted 9 lines · richard lucassen
I'm a newbie to tc and after some experimenting I have the following problem:
# tc qdisc show qdisc sfq 8006: dev ipsec0 quantum 1514b perturb 15secI can't get rid of this entry. Is there a way to clear all entries? I tried all sorts of "tc qdisc del xxx" but nothing seems to work. It says:
Did you delete its parent? If so, this is a bonafide bug. See also the 'bugs' section on http://www.docum.org
Regards,
bert
Signature · 8 lines
http://www.PowerDNS.com Versatile DNS Software & Services Trilab The Technology People Netherlabs BV / Rent-a-Nerd.nl - Nerd Available - 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
Quoted 3 lines · bert hubert
Did you delete its parent? If so, this is a bonafide bug. See also the 'bugs' section on http://www.docum.org
Hmmm, so it looks like I killed a parent with a still living child. I already noticed that when I try to kill a parent it says something like "device or resource busy". So this might be a bug. Unfortunately I don't know how to reproduce it. For the moment a reboot might be a solution, but I'd rather don't do that, but I fear I will have to.
Richard
Signature · 13 lines
___________________________________________________________________ The Linux documentation paradox: You have to know the answer before you ask the question +------------------------------------------------------------------+ | Richard Lucassen, Utrecht, Linux 2.4.14 RedHat 7.1 | | The Netherlands i686/1200MHz/512MB | | Public key: http://www.xs4all.nl/~pe1bbf/pubkey.asc | +------------------------------------------------------------------+ _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/