From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 112a09508e9538d67af9e60c207724eca49b1c51
Date: Thu, 05 Oct 2017 11:38:51 +0100 [thread overview]
Message-ID: <20171005103852.4073D1081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1734 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 112a09508e9538d67af9e60c207724eca49b1c51 (commit)
from bbc69f228db9e050e1b585a1ac09c495d32ef41a (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 112a09508e9538d67af9e60c207724eca49b1c51
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Oct 5 11:38:05 2017 +0100
core115: Add captive portal cron jobs to updater
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/115/update.sh | 8 ++++++++
1 file changed, 8 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/115/update.sh b/config/rootfiles/core/115/update.sh
index e0ee121..95260c8 100644
--- a/config/rootfiles/core/115/update.sh
+++ b/config/rootfiles/core/115/update.sh
@@ -48,6 +48,14 @@ ldconfig
openvpnctrl -s
openvpnctrl -sn2n
+grep -q "captivectrl" /var/spool/cron/root.orig || cat <<EOF >> /var/spool/cron/root.orig
+# Cleanup captive clients
+%hourly * /usr/bin/captive-cleanup
+
+# Reload captive firewall rules
+%nightly * 23-1 /usr/local/bin/captivectrl >/dev/null
+EOF
+fcrontab -z
# This update need a reboot...
#touch /var/run/need_reboot
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-10-05 10:38 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=20171005103852.4073D1081BA6@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