Moved the ulimit commands to the start function #363
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.
The placement of the
ulimit
calls in the current init script for Red Hat systems results in the commands being called every time the script is called. This means thatall result in the
ulimit
calls being executed.As far as I can see, this is unnecessary - they only need to be called when the service is starting.
While this isn't a problem itself, it can lead to some confusion. If a user runs
he'll receive
MongoDB did start correctly... but the
ulimit
calls were executed again when the user attempted to get the service's status. Because the user didn't run it withroot
privileges, the calls failed and resulted in an error. Once again, it's not a problem, but it can be confusing.— @citruspi