Debian init script should depend on networking, resolution and syslog #222
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
chrisboulton
force-pushed
the
debian-init
branch
from
f54eb05
to
9697505
Compare
|
Thanks! |
solarkennedy
added a commit
that referenced
this pull request
Jan 29, 2016
Debian init script should depend on networking, resolution and syslog
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.
I've had these changes sitting out in a branch for a while and have been meaning to submit them back.
I noticed we had issues with Consul starting in the wrong order on our systems - primarily because we were using syslog for logging and the syslog daemon hadn't been started by the time Debian had decided to start Consul.