From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0251dca9e865ca677aedc613e90c2a1ef96d2b0b
Date: Sun, 11 Aug 2013 09:47:00 +0200 [thread overview]
Message-ID: <20130811074700.7919020310@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1740 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 0251dca9e865ca677aedc613e90c2a1ef96d2b0b (commit)
from bdc9033f08bce0c76f7d134de4a21e2b11f3671e (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 0251dca9e865ca677aedc613e90c2a1ef96d2b0b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Aug 11 09:46:16 2013 +0200
core72: start ipsec only if enabled after update.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/72/update.sh | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/72/update.sh b/config/rootfiles/core/72/update.sh
index 15d1bf2..c3dc20a 100644
--- a/config/rootfiles/core/72/update.sh
+++ b/config/rootfiles/core/72/update.sh
@@ -34,7 +34,7 @@ done
#
#Stop services
-ipsec stop
+/etc/init.d/ipsec stop
/etc/init.d/snort stop
/etc/init.d/squid stop
@@ -47,7 +47,10 @@ extract_files
#Start services
/etc/init.d/squid start
/etc/init.d/snort start
-ipsec start
+if [ `grep "ENABLED=on" /var/ipfire/vpn/settings` ]; then
+ /etc/init.d/ipsec start
+fi
+
#
#Update Language cache
@@ -64,4 +67,3 @@ sync
sendprofile
#Don't report the exitcode last command
exit 0
-
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-08-11 7:47 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=20130811074700.7919020310@argus.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