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

Switch to using start-stop-daemon for consul upstart init script #130

Merged
merged 1 commit into from
May 31, 2015
Merged

Switch to using start-stop-daemon for consul upstart init script #130

merged 1 commit into from
May 31, 2015

Conversation

bdellegrazie
Copy link
Contributor

This avoids the use of sudo and permits passing the GOMAXPROCS setting
via the environment. In addition this change exposes the pid file again so
that other users can signal the agent.
Fixes #126

This avoids the use of sudo and permits passing the GOMAXPROCS setting
via the environment. In addition this change exposes the pid file again so
that other users can signal the agent.

Also fixed tests

Fixes #126
@solarkennedy
Copy link
Contributor

Thank you! As much as a I like the simplicity of the simple exec, I understand that the bugs are showstoppers.

solarkennedy added a commit that referenced this pull request May 31, 2015
Switch to using start-stop-daemon for consul upstart init script
@solarkennedy solarkennedy merged commit 9899cb1 into voxpupuli:master May 31, 2015
@bdellegrazie bdellegrazie deleted the upstart-GOMAXPROCS-fix branch May 31, 2015 18:58
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.

GOMAXPROCS discarded by upstart init due to sudo's env_reset option
2 participants