Exactly. If the user has set ensure => running, the service cannot be set
to disabled. So, unless one can specify the application order of
properties, the only thing one can do here is to check on syncing ensure
whether the service is disabled but shouldn't be. Of course, this will
cause multiple state changes and might unexpectedly cause the side-effect
of leaving services as Manual, which were Disabled formerly.

Best Regards, David

On Fri, 22 Jul 2011 12:27:15 -0700 (PDT), Cameron Thomas
<[email protected]> wrote:
> 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.

Reply via email to