Can you elaborate on that? Do you mean, as a default start-up state prior to attempting a move to 'running' state?
- Cameron On Jul 22, 12:35 am, David Schmitt <[email protected]> wrote: > On 21.07.2011 18:14, Jacob Helwig wrote: > > > We currently have the majority of the tests passing, marked as known > > failures due to missing providers or other yet unwritten code, or > > confined to not run on windows since they are testing functionality > > that we do not plan to support (running a master, for example). > > Awesome feat! > > > We've got a "Work in Progress" branch with a service provider for > > Windows that supports managing the "Start Type" (enabled), and whether > > the service is currently running (ensure) up on GitHub[1]. Currently, > > the provider does not work when transitioning a service from stopped > > with a start type of "disabled" to running with a start type of > > "automatic", or "manual". The problem is that the ResourceHarness > > always syncs ensure first, before syncing everything else, and Windows > > (understandably) refuses to start a "disabled" service. > > Shouldn't the windows' service provider set the service at least to > manual when trying to start it? > > Best Regards, David -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
