[chef-dev] Re: Re: Re: Re: CHEF-2880 debian policy and service provider

[Thom May < >]

On Fri, Feb 10, 2012 at 20:06, Tollef Fog Heen 
<
 >
 wrote:
> ]] Bryan McLellan
>
>> On Fri, Feb 10, 2012 at 1:42 PM, Tollef Fog Heen 
>> <
 >
>>  wrote:
>> > I think we shouldn't use invoke-rc.d, but rather use the service
>> > command.
>>
>> This sounds like reverting CHEF-597 [1], yes?
>
> Yup.
>
>> Other than Laurent's use case which we've come up with workarounds
>> for, is there any reason not to? This would fix CHEF-2880 simply by
>> ignoring the Debian service policy.
>
> Well, I guess Thom (who filed 597) could argue that if you've configured
> your system to not start $service, finding it running would be a
> surprise.  To that, I'd respond that manually calling /etc/init.d/foo or
> service foo start does not check run levels etc, and to me, doing
> explicit management in chef recipes is mentally much closer to calling
> service or the init script directly than it is to ask init to put the
> service in the state it should be in according to rcN.d.

Yeah, I was certainly thinking that if you had policy configured it
would be a surprise to find chef overriding it,
but i equally take your point that chef ought to be the definitive
source of truth for the system.
So I'm fine with reverting 597.
-Thom