From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5c8acc789b4756d942d5e465361eb6b8e3ebad4a
Date: Fri, 03 Nov 2017 16:20:02 +0000 [thread overview]
Message-ID: <20171103162002.5EA221081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1630 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 5c8acc789b4756d942d5e465361eb6b8e3ebad4a (commit)
from 9843bb7b5ad2517884f601a527e391953845e569 (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 5c8acc789b4756d942d5e465361eb6b8e3ebad4a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Nov 3 16:40:23 2017 +0100
core116: stop apache before extracting updated files
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/116/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/116/update.sh b/config/rootfiles/core/116/update.sh
index 84a4bb0..ebc98e1 100644
--- a/config/rootfiles/core/116/update.sh
+++ b/config/rootfiles/core/116/update.sh
@@ -33,6 +33,7 @@ done
# Stop services
/etc/init.d/snort stop
+/etc/init.d/apache stop
# Extract files
extract_files
@@ -44,7 +45,6 @@ ldconfig
#/usr/local/bin/update-lang-cache
# Start services
-/etc/init.d/apache stop
/etc/init.d/apache start
/etc/init.d/snort start
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-11-03 16:20 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=20171103162002.5EA221081BCF@git01.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