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

Service command handling fix when no upstart config file #2231

Merged
merged 1 commit into from
Feb 28, 2013
Merged

Service command handling fix when no upstart config file #2231

merged 1 commit into from
Feb 28, 2013

Conversation

tonk
Copy link
Contributor

@tonk tonk commented Feb 28, 2013

Fixed the service command not working

On Ubuntu 1[02].04 the service name was not recognized because
there is a SysV style init script, but not an upstart config file.

Example: The ntp client.

Also removed extra spaces at the end of the lines, while at it.

commit e057ea671395ec8847f920a63cf9524f5c8fde5f
Author: Ton Kersten <tonk@tonkersten.com>
Date:   Thu Feb 28 13:02:25 2013 +0100

    Fixed the service command not working

    On Ubuntu 1[02].04 the service name was not recognized because
    there is a SysV style init script, but not an upstart config file.

    Example: The `ntp` client.

    Also removed extra spaces at the end of the lines, while at it.
mpdehaan added a commit that referenced this pull request Feb 28, 2013
Service command handling fix when no upstart config file
@mpdehaan mpdehaan merged commit 6c9bb35 into ansible:devel Feb 28, 2013
@mpdehaan
Copy link
Contributor

Merged in, thanks!

@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
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.

None yet

2 participants