summaryrefslogtreecommitdiffstats
path: root/src/usr/local/www/status_queues.php
diff options
context:
space:
mode:
authorPhil Davis <phil.davis@inf.org>2016-06-27 14:30:14 +0930
committerChris Buechler <cmb@pfsense.org>2016-06-27 14:16:13 -0500
commitaceaf18c1ad93c808b77e0bbf324949d5d2eede0 (patch)
treecc34e086600b4a481586e35eb6142a1b46799679 /src/usr/local/www/status_queues.php
parent9d265a8db874249ac16d4d02ce68463416f1aee2 (diff)
downloadpfsense-aceaf18c1ad93c808b77e0bbf324949d5d2eede0.zip
pfsense-aceaf18c1ad93c808b77e0bbf324949d5d2eede0.tar.gz
Always use require_once
The usage of require() and require_once() throughout the system is inconsistent, and "bugs" come up now and then when the order of "requires" is a bit different and some require() happens after the include file is already included/required. It seems to me that there is no harm at all in always using require_once().
Diffstat (limited to 'src/usr/local/www/status_queues.php')
-rw-r--r--src/usr/local/www/status_queues.php2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/usr/local/www/status_queues.php b/src/usr/local/www/status_queues.php
index 52d6773..9362163 100644
--- a/src/usr/local/www/status_queues.php
+++ b/src/usr/local/www/status_queues.php
@@ -66,7 +66,7 @@ header("Cache-Control: no-cache, no-store, must-revalidate"); // HTTP/1.1
header("Pragma: no-cache"); // HTTP/1.0
*/
-require("guiconfig.inc");
+require_once("guiconfig.inc");
class QueueStats {
public $queuename;
public $queuelength;
OpenPOWER on IntegriCloud