Skip to content

Optionally manage the mysqld service #122

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

Merged
merged 2 commits into from
Oct 5, 2012

Conversation

hunner
Copy link
Contributor

@hunner hunner commented Oct 4, 2012

When using failover options such as Corosync, it's preferable to allow the failover software to manage the starting and stopping of the service. This parameter allows that to happen.

hunner added 2 commits October 4, 2012 16:20
When using failover options such as Corosync, it's preferable to allow the failover software to manage the starting and stopping of the service. This parameter allows that to happen.
bodepd added a commit that referenced this pull request Oct 5, 2012
Optionally manage the mysqld service
@bodepd bodepd merged commit c84ffde into puppetlabs:master Oct 5, 2012
pmcmaw pushed a commit to pmcmaw/puppetlabs-mysql that referenced this pull request Mar 3, 2021
(PDK-1501) Fix acceptance stages in Travis CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants