From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: openwrt-devel@lists.openwrt.org, luis@bitamins.net,
cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] [sqm-scripts] not started at boot?
Date: Sun, 15 Feb 2015 14:39:46 +0000 [thread overview]
Message-ID: <54E0AFB2.5040806@gmail.com> (raw)
Hi Toke
I tried installing sqm-scripts from trunk, on Barrier Breaker on my
wndr3800.
It's very effective, but I notice SQM isn't applied at boot time. The
system log complains about pppoe-wan interface not existing, when the
sqm init script is started.
My guess is it'd be the same even if my WNDR was running the base system
from trunk. Because the sqm scripts don't have nice integration like
the qos scripts package.
Is that useful enough as a bug report? Do you need me to work on a
proper patch?
qos-scripts has a hotplug script, so I copied it for sqm and the problem
is "fixed". Though my stupid script re-runs the sqm as every single
network interface comes up, so it spams the log and probably slows
things down a bit. (Maybe sqm script also wants to not be so noisy in
the log)
cat <<EOF > /etc/hotplug.d/iface/10-sqm
#!/bin/sh
# my sqm isn't being enabled on boot
# cargo-cult this hotplug script from qos-scripts
[ "$ACTION" = ifup ] && /etc/init.d/sqm enabled && /usr/lib/sqm/run.sh
EOF
next reply other threads:[~2015-02-15 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 14:39 Alan Jenkins [this message]
2015-02-15 15:00 ` Toke Høiland-Jørgensen
2015-02-15 15:48 ` Sebastian Moeller
2015-02-15 15:56 ` Toke Høiland-Jørgensen
2015-02-15 16:12 ` Sebastian Moeller
2015-02-15 16:18 ` Toke Høiland-Jørgensen
2015-02-16 23:23 ` Sebastian Moeller
2015-02-15 16:33 ` Alan Jenkins
2015-02-16 9:05 ` Sebastian Moeller
2015-03-03 17:06 ` Sebastian Moeller
2015-03-03 21:23 ` Alan Jenkins
2015-03-03 21:27 ` Toke Høiland-Jørgensen
2015-03-03 21:35 ` Sebastian Moeller
2015-03-03 22:39 ` Alan Jenkins
2015-03-03 22:46 ` Sebastian Moeller
2015-02-15 16:16 ` Sebastian Moeller
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E0AFB2.5040806@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=luis@bitamins.net \
--cc=openwrt-devel@lists.openwrt.org \
--cc=toke@toke.dk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox