From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] effaff: Fix SQM tear down on interfaces that are just dele...
Date: Thu, 09 Oct 2014 12:59:06 -0700 [thread overview]
Message-ID: <5436e90a19ef7_50fc3f833a7ef2a058f5@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.10
Commit: effaffa1f2a8f60c305391f6e7025b95e72e9d7a
https://github.com/dtaht/ceropackages-3.10/commit/effaffa1f2a8f60c305391f6e7025b95e72e9d7a
Author: Sebastian Moeller <moeller0@gmx.de>
Date: 2014-10-09 (Thu, 09 Oct 2014)
Changed paths:
M net/sqm-scripts/files/usr/lib/sqm/run.sh
Log Message:
-----------
Fix SQM tear down on interfaces that are just deleted or changed in uci
Up until now SQM tried to use the uci config file /etc/config/sqm
to figure out on which interfaces it was running. Unfortunatelly,
the uci config file is a bad place to save this state, as the user
can change the interface for a given section and thereby wiping out
the information about the previous interface, whileSQM might still
be active on the old interface. To partly deal with this issue
SQM had started to create its own state file to mark interfaces
with active SQM instances. Instead of using the interfaces from the
config file just use these state fils to figure out which interfaces
might need to be stopped. And since all current qos scrpts start out
with tearing down any traffic shaping infrastructure on its main
interface and the associated IFB, we just stop all active SQM instances
before potentially starting new ones. This needs testing...
reply other threads:[~2014-10-09 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5436e90a19ef7_50fc3f833a7ef2a058f5@hookshot-fe2-cp1-prd.iad.github.net.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/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