From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. dea399178ec1cb67d8235cc476a82dcd6a24080c
Date: Sat, 24 Aug 2013 17:20:17 +0200 [thread overview]
Message-ID: <20130824152041.3E4E420542@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1520 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 dea399178ec1cb67d8235cc476a82dcd6a24080c (commit)
from 2aecef3e59f4e63dfb781b4e2493edbd6225268d (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 dea399178ec1cb67d8235cc476a82dcd6a24080c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Aug 24 17:19:36 2013 +0200
tor: Fix initscript (again).
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/tor | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/src/initscripts/init.d/tor b/src/initscripts/init.d/tor
index 4fef577..d631e86 100644
--- a/src/initscripts/init.d/tor
+++ b/src/initscripts/init.d/tor
@@ -9,13 +9,13 @@
. /etc/sysconfig/rc
. ${rc_functions}
+eval $(/usr/local/bin/readhash /var/ipfire/tor/settings)
+
function tor_is_enabled() {
[ "${TOR_ENABLED}" = "on" ] || [ "${TOR_RELAY_ENABLED}" = "on" ]
}
function setup_firewall() {
- eval $(/usr/local/bin/readhash /var/ipfire/tor/settings)
-
# Flush all rules.
flush_firewall
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-08-24 15: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=20130824152041.3E4E420542@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