diff options
| author | Phil Davis <phil.davis@inf.org> | 2015-06-15 14:19:11 +0545 |
|---|---|---|
| committer | Phil Davis <phil.davis@inf.org> | 2015-06-15 14:19:11 +0545 |
| commit | 6c07db487164262f9191ad02805523bd153e0ba6 (patch) | |
| tree | 0c266356179ac730233a16c0e3767a0c22514c4d /etc/inc/config.lib.inc | |
| parent | 67d9685607eef7c679fda929ad4855be1b2f9dec (diff) | |
| download | pfsense-6c07db487164262f9191ad02805523bd153e0ba6.zip pfsense-6c07db487164262f9191ad02805523bd153e0ba6.tar.gz | |
Code spacing
and other random stuff I noticed.
I think this finishes messing with code style. The codebase should match
the developer style guide closely enough that 99.9% of changes will not
feel the need to also massage the formatting.
Diffstat (limited to 'etc/inc/config.lib.inc')
| -rw-r--r-- | etc/inc/config.lib.inc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/etc/inc/config.lib.inc b/etc/inc/config.lib.inc index 29c8817..5eb3d5c 100644 --- a/etc/inc/config.lib.inc +++ b/etc/inc/config.lib.inc @@ -898,9 +898,10 @@ function backup_config() { function set_device_perms() { $devices = array( - 'pf' => array( 'user' => 'root', - 'group' => 'proxy', - 'mode' => 0660), + 'pf' => array( + 'user' => 'root', + 'group' => 'proxy', + 'mode' => 0660), ); foreach ($devices as $name => $attr) { @@ -975,8 +976,7 @@ function pfSense_clear_globals() { $errorstr = "PHP ERROR: Type: {$error['type']}, File: {$error['file']}, Line: {$error['line']}, Message: {$error['message']}"; print($errorstr); log_error($errorstr); - } else - if ($error['type'] != E_NOTICE) { + } else if ($error['type'] != E_NOTICE) { $errorstr = "PHP WARNING: Type: {$error['type']}, File: {$error['file']}, Line: {$error['line']}, Message: {$error['message']}"; // XXX: comment out for now, should re-enable post-2.2 //print($errorstr); |
