Allow user-defined service restart parameter. #57
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 allows, for example, on CentOS/Debian/Ubuntu us to use /etc/init.d/haproxy reload to restart haproxy when config changes, which:
Without this it's easy to push out a option with, say a typo in it, which will cause haproxy to be left in a stopped state with broken config, because /etc/init.d/haproxy restart stops haproxy then starts it.
An alternative way to achieve this would be some logic to set an appropriate restart command for each distro, but I shied away from this, because it would presumably have to take into account things like Fedora's move to systemd.