Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suricata5 LOG_WARNING fix. Issue #10751 #899

Closed
wants to merge 1 commit into from

Conversation

vktg
Copy link
Contributor

@vktg vktg commented Jul 10, 2020

Rename LOG_WARN to LOG_WARNING

https://www.php.net/manual/en/function.syslog.php:

Constant Description
LOG_EMERG system is unusable
LOG_ALERT action must be taken immediately
LOG_CRIT critical conditions
LOG_ERR error conditions
**LOG_WARNING warning conditions**
LOG_NOTICE normal, but significant, condition
LOG_INFO informational message
LOG_DEBUG debug-level message

@bmeeks8
Copy link
Contributor

bmeeks8 commented Jul 10, 2020

I'm about ready to post the update to Suricata 5.0.3. That update will remove Barnyard2 from Suricata and also has a large number of other enhancements and fixes in it. I also pulled the changes from this request into mine, so let's just close this Pull Request with the knowledge that the fixes for LOG_WARN needing to be LOG_WARNING instead are carried over into the upcoming pfSense-pkg-suricata-5.0.3 update.

@rbgarga rbgarga closed this Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants