From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f48920d84f72235c5141e32772d5c8a447f9900e
Date: Fri, 18 Oct 2019 21:09:15 +0000 [thread overview]
Message-ID: <46vzDW4Cqwz2xqV@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via f48920d84f72235c5141e32772d5c8a447f9900e (commit)
from 596c71d07fb2fc564844684a5692d598edf3d647 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit f48920d84f72235c5141e32772d5c8a447f9900e
Author: Daniel Weismüller <daniel.weismueller(a)ipfire.org>
Date: Fri Oct 18 16:59:49 2019 +0200
core137: Remove imq0 and unload imq module after QoS has been stopped
Signed-off-by: Daniel Weismüller <daniel.weismueller(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/137/update.sh | 6 ++++++
1 file changed, 6 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/137/update.sh b/config/rootfiles/core/137/update.sh
index da87f9430..dcbd8112a 100644
--- a/config/rootfiles/core/137/update.sh
+++ b/config/rootfiles/core/137/update.sh
@@ -83,6 +83,12 @@ rm -rf /lib/modules
# Stop services
/usr/local/bin/qosctrl stop
+# Delete imq0 if it is still present after QoS has been stopped
+if [ -d "/sys/class/net/imq0" ]; then
+ ip link del dev imq0
+ modprobe -r imq
+fi
+
# Extract files
extract_files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-10-18 21:09 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=46vzDW4Cqwz2xqV@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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