Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
engine: choose better Suricata logging levels for rule test
The current default is to use SC_LOG_LEVEL=warning which can output non-fatal warnings which is generally not what you want when running from cron with "suricata-update -q". Now, if "-q" is provided, run Suricata with SC_LOG_LEVEL=error which is useful for cron to ony be notified of fata errors. Generally end-users are not worried about rule warnings such as: ja3.hash should not be used together with nocase, since the rule is automatically lowercased anyway which makes nocase redundant. This also allows for log level be set with SC_LOG_LEVEL, in which case Suricata-Update will not change the log level. Additionally, make Suricata more verbose if Suricata-Update is run with "-v". Ticket: https://redmine.openinfosecfoundation.org/issues/7494
- Loading branch information