summaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
authorPhil Davis <phil.davis@inf.org>2015-03-02 22:48:59 +0545
committerPhil Davis <phil.davis@inf.org>2015-03-02 22:48:59 +0545
commit860842334c922e719b7fb137e6348098eb8f937e (patch)
treebb6859391b13d59358e3c6812db5ca1db7b380f3 /etc
parent8f5f40c9fca0bfb637589b4c86e53bfb80753c87 (diff)
downloadpfsense-860842334c922e719b7fb137e6348098eb8f937e.zip
pfsense-860842334c922e719b7fb137e6348098eb8f937e.tar.gz
Be safe use require_once in zeromq
I was testing code and just doing stuff like: require_once("zeromq.inc"); in Diagnostics->Command Prompt, PHP Execute That brings an error because underneath that PHP Execute code it has already included auth.inc I guess zeromq.inc is used quite separately to the rest of the system, and must be OK just having a "require" here. But it seems safer to always use require_once, just in case it gets called in a new way/sequence. Comments welcome.
Diffstat (limited to 'etc')
-rw-r--r--etc/inc/zeromq.inc2
1 files changed, 1 insertions, 1 deletions
diff --git a/etc/inc/zeromq.inc b/etc/inc/zeromq.inc
index 65589d0..a8503fc 100644
--- a/etc/inc/zeromq.inc
+++ b/etc/inc/zeromq.inc
@@ -32,7 +32,7 @@ define('ZEROMQ_TRUE', 'true');
define('ZEROMQ_FASLE', 'false');
$do_not_include_config_gui_inc = true;
-require("auth.inc");
+require_once("auth.inc");
//$debug = true;
OpenPOWER on IntegriCloud