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.

Sign up for GitHub

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

Jump to bottom

Calling /etc/init.d/consul restart sometimes ends up with a stopped … #427

Merged
merged 1 commit into from
May 7, 2017
Merged

Calling /etc/init.d/consul restart sometimes ends up with a stopped … #427

merged 1 commit into from
May 7, 2017

Commits on Apr 27, 2017

  1. Calling /etc/init.d/consul restart sometimes ended up with a stopped … 

    …consul process. The reason was that it would sometimes start consul before it was completely stopped. This can be easily reproduced runnning:

 watch -n 0.5 -e '/etc/init.d/consul restart; sleep 0.1; /etc/init.d/consul status'

Adding the --retry parameter lets start-stop-daemon wait until the consul process is actually stopped.
    @MichaelKueller
    MichaelKueller committed Apr 27, 2017
    Configuration menu
    Copy the full SHA
    a723491 View commit details
    Browse the repository at this point in the history