public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. d4af85f252c5e1573f548377ea97928adf07c4d0
Date: Fri, 04 Nov 2016 18:26:54 +0000	[thread overview]
Message-ID: <20161104182700.B0B1F1081BA5@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2845 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, master has been updated
       via  d4af85f252c5e1573f548377ea97928adf07c4d0 (commit)
       via  08fc1aa43b293dccf211b8f961a6d1b7606ed352 (commit)
      from  7ebc0a16e23b438fb79e981be0fda612cf17fdcb (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 d4af85f252c5e1573f548377ea97928adf07c4d0
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Fri Nov 4 18:23:25 2016 +0000

    unbound: Send out replies from where they came in
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

commit 08fc1aa43b293dccf211b8f961a6d1b7606ed352
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Fri Nov 4 17:46:24 2016 +0000

    core107: Restart unbound to activate configuration changes
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/core/107/filelists/files | 1 +
 config/rootfiles/core/107/update.sh       | 3 +++
 config/unbound/unbound.conf               | 2 +-
 3 files changed, 5 insertions(+), 1 deletion(-)

Difference in files:
diff --git a/config/rootfiles/core/107/filelists/files b/config/rootfiles/core/107/filelists/files
index 1dc0a35..226f45b 100644
--- a/config/rootfiles/core/107/filelists/files
+++ b/config/rootfiles/core/107/filelists/files
@@ -1,5 +1,6 @@
 etc/system-release
 etc/issue
+etc/unbound/unbound.conf
 etc/rc.d/init.d/unbound
 srv/web/ipfire/cgi-bin/logs.cgi/log.dat
 srv/web/ipfire/cgi-bin/traffic.cgi
diff --git a/config/rootfiles/core/107/update.sh b/config/rootfiles/core/107/update.sh
index dd6b33e..276dae5 100644
--- a/config/rootfiles/core/107/update.sh
+++ b/config/rootfiles/core/107/update.sh
@@ -178,6 +178,9 @@ if [ `grep "ENABLED=on" /var/ipfire/vpn/settings` ]; then
 	/etc/init.d/ipsec start
 fi
 
+# Restart unbound to activate configuration changes
+/etc/init.d/unbound restart
+
 # Delete old QoS enabled indicator
 rm -f /var/ipfire/qos/enable
 
diff --git a/config/unbound/unbound.conf b/config/unbound/unbound.conf
index a6cdc4d..3f724d8 100644
--- a/config/unbound/unbound.conf
+++ b/config/unbound/unbound.conf
@@ -62,7 +62,7 @@ server:
 	use-caps-for-id: no
 
 	# Listen on all interfaces
-	interface-automatic: no
+	interface-automatic: yes
 	interface: 0.0.0.0
 
 	# Allow access from everywhere


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2016-11-04 18:26 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=20161104182700.B0B1F1081BA5@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