From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core137, updated. 6e414ea1e072133501d44002c857e1d7cbf2b076
Date: Sun, 20 Oct 2019 09:53:50 +0000 [thread overview]
Message-ID: <46ww8G4jgnz2xxH@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1666 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, core137 has been updated
via 6e414ea1e072133501d44002c857e1d7cbf2b076 (commit)
from f48920d84f72235c5141e32772d5c8a447f9900e (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 6e414ea1e072133501d44002c857e1d7cbf2b076
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Oct 20 09:51:04 2019 +0000
core137: don't start QoS
QoS need to load kernel modules but the currect kernel
was removed so it cannot correct start without a reboot.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/137/update.sh | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/137/update.sh b/config/rootfiles/core/137/update.sh
index dcbd8112a..f9cfd9ba0 100644
--- a/config/rootfiles/core/137/update.sh
+++ b/config/rootfiles/core/137/update.sh
@@ -110,7 +110,6 @@ rm -f /etc/sysconfig/lm_sensors
# generate new qos script
/usr/local/bin/qosctrl generate
-/usr/local/bin/qosctrl start
# Search sensors again after reboot into the new kernel
rm -f /etc/sysconfig/lm_sensors
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-10-20 9:53 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=46ww8G4jgnz2xxH@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