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

NSM: when (re)starting Suricata, make sure stats.log has proper ownership #1477

Closed
dougburks opened this Issue Mar 7, 2019 · 2 comments

Comments

Projects
1 participant
@dougburks
Copy link
Contributor

dougburks commented Mar 7, 2019

Related to #1456

If stats.log doesn't already exist, it will get created by truncate but with incorrect ownership (root:root instead of sguil:sguil).

@dougburks dougburks self-assigned this Mar 7, 2019

@dougburks dougburks added this to To do in 16.04.6.1 via automation Mar 7, 2019

@dougburks dougburks changed the title NSM: when (re)starting Suricata, only truncate stats.log if the file exists NSM: when (re)starting Suricata, make sure stats.log has proper ownership Mar 7, 2019

dougburks added a commit to Security-Onion-Solutions/securityonion-nsmnow-admin-scripts that referenced this issue Mar 7, 2019

@dougburks dougburks moved this from To do to In progress in 16.04.6.1 Mar 7, 2019

@dougburks dougburks moved this from In progress to In Testing in 16.04.6.1 Mar 7, 2019

@dougburks

This comment has been minimized.

Copy link
Contributor Author

dougburks commented Mar 7, 2019

@dougburks

This comment has been minimized.

Copy link
Contributor Author

dougburks commented Mar 11, 2019

@dougburks dougburks closed this Mar 11, 2019

16.04.6.1 automation moved this from In Testing to Done Mar 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.