[dtaht/ceropackages-3.10] effaff: Fix SQM tear down on interfaces that are just dele...

[dtaht/ceropackages-3.10] effaff: Fix SQM tear down on interfaces that are just dele...

[GitHub]

[-- 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...