From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c8b574c3078b35c272960ac0b26de6dded845467
Date: Sun, 01 Mar 2020 21:55:17 +0000 [thread overview]
Message-ID: <48VxsL290Rz2y9T@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1802 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 c8b574c3078b35c272960ac0b26de6dded845467 (commit)
from 770a1507dd750fe98f327919c9da576d6b996469 (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 c8b574c3078b35c272960ac0b26de6dded845467
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Mar 1 21:54:28 2020 +0000
core142: stop squid and suricata while update
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/142/update.sh | 5 +++++
1 file changed, 5 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/142/update.sh b/config/rootfiles/core/142/update.sh
index 581e8fd19..bf63f58ca 100644
--- a/config/rootfiles/core/142/update.sh
+++ b/config/rootfiles/core/142/update.sh
@@ -88,6 +88,8 @@ rm -rf /usr/lib/python2.7/site-packages/ddns
rm -rf /usr/lib/pppd/2.4.7
# Stop services
+/etc/init.d/squid stop
+/etc/init.d/suricata stop
# Extract files
extract_files
@@ -121,6 +123,9 @@ done
/usr/local/bin/filesystem-cleanup
# Start services
+/etc/init.d/unbound restart
+/etc/init.d/suricata start
+/etc/init.d/squid start
# remove lm_sensor config after collectd was started
# to reserch sensors at next boot with updated kernel
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-03-01 21:55 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=48VxsL290Rz2y9T@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