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

Change the service creation to use the service_name attribute throughout #368

Merged
merged 2 commits into from
Jul 1, 2015

Conversation

rocpatel
Copy link

The service_name attribute was only used to define the service. However,
the restart_command and reload_command for rhel had a hardcoded service_name
in it. So, for example Software Collections has an apache2.4 rpm package for
redhat 6 that installs the httpd service under a different name 'httpd24-httpd'.
The recipe would fail at service creation even though I overwrote the service_name
attribute.

The service_name attribute was only used to define the service.  However,
the restart_command and reload_command for rhel had a hardcoded service_name
in it.  So, for example Software Collections has an apache2.4 rpm package for
redhat 6 that installs the httpd service under a different name 'httpd24-httpd'.
The recipe would fail at service creation even though I overwrote the service_name
attribute.
when 'debian'
provider Chef::Provider::Service::Debian
when 'arch'
service_name 'httpd'
service_name apache_service_name

This comment was marked as outdated.

This comment was marked as outdated.

Previous commit would break arch, so I defaulted the service_name
to httpd
@svanzoest svanzoest self-assigned this Jul 1, 2015
svanzoest added a commit that referenced this pull request Jul 1, 2015
Change the service creation to use the service_name attribute throughout
@svanzoest svanzoest merged commit 278619a into sous-chefs:master Jul 1, 2015
@svanzoest
Copy link
Contributor

Thanks!

@lock lock bot unassigned svanzoest Jul 24, 2018
@lock
Copy link

lock bot commented Jul 24, 2018

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 Jul 24, 2018
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