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.

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 custom template for "sysvinit" service provider #266

Merged
merged 1 commit into from
Jan 28, 2016

Conversation

legal90
Copy link
Contributor

@legal90 legal90 commented Jan 28, 2016

The default template looks very tricky and it doesn't work well on RHEL 6: there are some artifacts in the console output while we are doing service consul <stop | start>:
https://github.com/poise/poise-service/blob/d9a5135dbe5711214c377c8ee2e7af029b1f10b7/chef/templates/default/sysvinit.sh.erb

This PR adds a custom template for sysvinit provider which looks pretty clear and works fine.
It was inspired by the init script form "consul-rpm" project: consul.init

Verified on CentOS 6.7 and Debian 7.9

P.s. This PR could be related to #235, but it doesn't fix that issue. For RHEL/CentOS 6 we still have to set provider to :sysvinit in explicit to avoid the usage of :upstart (#235 (comment)).

@johnbellone
Copy link
Contributor

👍

@@ -48,7 +48,7 @@ def command(config_file, config_dir)
if windows?
%{agent -config-file="""#{config_file}""" -config-dir="""#{config_dir}"""}
else
"/usr/bin/env consul agent -config-file=#{config_file} -config-dir=#{config_dir}"

This comment was marked as outdated.

johnbellone added a commit that referenced this pull request Jan 28, 2016
Add custom template for "sysvinit" service provider
@johnbellone johnbellone merged commit 62f5c06 into sous-chefs:master Jan 28, 2016
@legal90 legal90 deleted the sysvinit-tpl branch January 28, 2016 13:09
@lock
Copy link

lock bot commented Apr 25, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants