SCLogFGFilterFile *sc_log_fg_filters[SC_LOG_FILTER_MAX] = { NULL, NULL };
/**
- * \brief Mutex for accessing the fine-grained fiters sc_log_fg_filters
+ * \brief Mutex for accessing the fine-grained filters sc_log_fg_filters
*/
static SCMutex sc_log_fg_filters_m[SC_LOG_FILTER_MAX] = { SCMUTEX_INITIALIZER,
SCMUTEX_INITIALIZER };
* of the FG filters. If there is a match it rejects the logging
* for that messages, else it allows that message to be logged
*
- * \praram file File_name from where the log_message originated
+ * \param file File_name from where the log_message originated
* \param function Function_name from where the log_message originated
* \param line Line number from where the log_message originated
*
* allows messages that match this filter, to be logged, while the filter
* is defined using a file_name, function_name and line_number.
*
- * If a particular paramter in the fg-filter(file, function and line),
+ * If a particular parameter in the fg-filter(file, function and line),
* shouldn't be considered while logging the message, one can supply
* NULL for the file_name or function_name and a negative line_no.
*
* allows messages that don't match this filter, to be logged, while the
* filter is defined using a file_name, function_name and line_number
*
- * If a particular paramter in the fg-filter(file, function and line),
+ * If a particular parameter in the fg-filter(file, function and line),
* shouldn't be considered while logging the message, one can supply
* NULL for the file_name or function_name and a negative line_no.
*
/**
* \brief Macro used to log debug messages on function exit. Comes under the
- * debugging sybsystem, and hence will be enabled only in the presence
+ * debugging subsystem, and hence will be enabled only in the presence
* of the DEBUG macro. Apart from logging function_exit logs, it also
* processes the FD filters, if any FD filters are registered. This
* function_exit macro should be used for functions that returns a