sysv & debian init updates to kill or leave #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes voxpupuli#85. The 'stop' action in init scripts for sysv and Debian will only 'leave' the cluster if acting as an agent. When running as a server, as determined by a call to `consul info`, kill the process instead. Both updates also enforce the use of a PID file located in a /var/run/consul directory, writeable by the consul::user configured in Puppet.
|
I haven't tested this in AWS or Debian. Please test. Works great in Centos 6.6. |
|
Thanks! |
solarkennedy
added a commit
that referenced
this pull request
Feb 26, 2015
sysv & debian init updates to kill or leave
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes #85. The 'stop' action in init scripts for sysv and Debian
will only 'leave' the cluster if acting as an agent. When running as a
server, as determined by a call to
consul info, kill the processinstead.
Both updates also enforce the use of a PID file located in a
/var/run/consul directory, writeable by the consul::user configured in
Puppet.