summaryrefslogtreecommitdiffstats
path: root/etc/inc/zeromq.inc
diff options
context:
space:
mode:
authorPhil Davis <phil.davis@inf.org>2015-03-02 22:48:59 +0545
committerRenato Botelho <garga@FreeBSD.org>2015-03-03 08:01:40 -0300
commit603a97cb57dab50279da0fb94caf03f9d3dd1d26 (patch)
tree330d7fd13d54fb3a2cac602401dbc61cd90dc267 /etc/inc/zeromq.inc
parent911cc213abd60d2d090778a080ac144e9501716a (diff)
downloadpfsense-603a97cb57dab50279da0fb94caf03f9d3dd1d26.zip
pfsense-603a97cb57dab50279da0fb94caf03f9d3dd1d26.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/inc/zeromq.inc')
-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