-
-
Notifications
You must be signed in to change notification settings - Fork 244
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.
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
add upstart init #71
add upstart init #71
Conversation
Hi. I think it's a good idea to add upstart support. But I don't like the implementation, because the I think it's better to check everywhere in the code where we call |
The init script runs |
it look like upstart sends the appropriate SIGHUP for the reload The restart is a SIGTERM followed by a start & that can be reconfigured as well. |
@@ -149,6 +158,7 @@ | |||
end | |||
|
|||
service 'consul' do | |||
provider Chef::Provider::Service::Upstart if platform?("ubuntu") |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This PR is not BC. More often, it's a big BC break, because on existing node, I had consul with init.d and now, I have both init and upstart. And so chef failed:
|
Hi, Sorry to "spam" this thread, but what id the right procedure to migrate ? |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Native upstart service for Ubuntu, it behaves identically to the sysvinit script. Anyone upgrading will get blessed with 2 init files which might cause a bit of confusion.