Fix the GOMAXPROCS warning for Upstart-based systems #39
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.
Description
Improvements to the Upstart startup script:
GOMAXPROCS=2
GOMAXPROCS
configurable via/etc/default/consul
setuid
/setgid
Testing Done
Tested on Ubuntu 12.04:
Saw no more warnings about
GOMAXPROCS
in/var/log/upstart/consul.log
using the default configIf I set
GOMAXPROCS=1
in/etc/default/consul
, the warning comes back so the sourcing of that file is working.Saw that
consul
was started with the correct uid/gid :Verified that
service consul restart
andservice consul reload
both work as expected.