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.
Prompted by @solarkennedy’s reply, here is how I think the Systemd unit file should look.
One thing that is not addressed in the very detailed commit message is the request for “some good data on what [the value of
RestartSec
] should be”. My reasoning for removing this option and keeping the default is as follows:My intuition tells me that we want to respawn Consul immediately on failure, without any delay. This would have meant setting
RestartSec=0ms
.The creators of Systemd, and Systemd itself by extension, are notorious for being very opinionated. If they deemed that the default should be 100ms and not 0ms, and given that I don’t have data to support my preference, I will rather trust their judgement.
The full commit message follows: