Bug #15734
openSyslog priority levels shouldn't default to ERR
0%
Description
Too much syslog output from pfSense is emitted as priority ERR when it's not. I believe this is due the the presence, in src/etc/inc/util.inc, of log_error(), but no similar functions for more nuanced reporting, such as log_warn, log_notice, log_info, or log_debug. Or just a parameterized generic log_message($message, $priority) function?
As an example, rc.filtersynchonize only emits ERR, even if the message is as benign as "Nothing has been configured to be synched. Skipping...."
Likewise, xmlrpc_client.inc makes five calls to log_error, even though two of these are the "Beginning XMLRPC sync..." and "XMLRPC reload data success ..."
There are just over 1200 calls to log_error in the codebase. How many of these are actually ERR level events?
Couldn't we get more finely grained logging? pfSense is a serious product, but the logging is so noisy as to be nearly useless.
Files
No data to display