Issue #8272 has been updated by Nick Lewis. Status changed from Accepted to Merged - Pending Release
Merged some more fixes in commit:1809b40e5ab05ceac166d5271cf1fe392efee1e1. This should close out this feature for now. If a service is disabled and we are ensure => running, the behavior depends on whether we are managing enable. If we are, then we will enable the service (automatic start if enable => true, otherwise manual), and then start the service. Then enable will be synced, if appropriate, re-disabling the service if that's what's desired. If we're not managing enable, we will refuse to start, and tell the user to set enable => false if running and disabled is *really* the desired state. ---------------------------------------- Feature #8272: Windows Services Management https://projects.puppetlabs.com/issues/8272 Author: Cameron Thomas Status: Merged - Pending Release Priority: Normal Assignee: Category: windows Target version: Telly Affected Puppet version: Keywords: Branch: Create provider to manage Windows services via the registry. Should start,/stop, pause/restart enable/disable existing services. No requirement to install or remove. No DACLs, just ensure/enable as per other providers. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
