- From: Steven Danna <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Point of service resource *_command attrs?
- Date: Sat, 22 Nov 2014 14:26:30 +0000
Hi,
You might have luck setting the `provider` for the resource to
Chef::Provider::Service::Simple. You'll need to specify a command for
any action you want. And, unfortunately, the Simple provider doesn't
have a hook for the enable action, so you would need to change your
action to just :start. Definitely looks like there is some cleanup to
do in the service provider implementations there.
On Sat, Nov 22, 2014 at 1:19 AM, Lamont Granquist
<
>
wrote:
>
On 11/21/14, 1:33 PM, Jeff Blaine wrote:
>
>
>
> I can't figure out what the *_command attributes are actually for.
>
>
>
> Setting init_command, start_command ... etc... to a value seems
>
> pointless when the chosen underlying provider has all of its hardcoded
>
> information that it uses.
>
>
>
> service 'foo' do
>
> init_command '/bin/true'
>
> start_command '/bin/true'
>
> action [:enable, :start]
>
> end
>
>
>
> ==> "unable to locate the init.d script!"
>
>
>
> Any ideas?
>
>
>
I think there's some outstanding bugs where the providers assume they know
>
best, and really need to respect the resource attributes given by the user
>
so that the user can override. Those are just bugs in the provider
>
implementation. However, I don't have any good workaround suggestions other
>
than submitting pull-requests and unfortunately don't have the bandwidth
>
right now.
>
Archive powered by MHonArc 2.6.16.