This repository has been archived by the owner on Apr 19, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When SecurityOnion is installed, but not yet configured, on a base Ubuntu 12.04.5 server install, it creates the watchdog cron.d entry which is called every five minutes. However, the sguil user has not yet been created, so nsm_sensor_ps-restart calls adduser with an invalid username, and the error is sent to stderr, which generates an email to the default user every five minutes.
By redirecting stderr to stdout (before redirecting stdout to /dev/null), when adduser is called before sosetup is run (sguil user does not yet exist), the adduser error shows up in /var/log/nsm/watchdog.log rather than being mailed to root.