Hi Forrie,
Puppet service resource *enable* property internally executes the
chkconfig command for red hat, This property behaves quite differently
depending on the platform; wherever possible, it relies on local tools to
enable or disable a given service.You can confirm the facter *osfamily *returns
*redhat *or not. Use provider => redhat along with enable property. Thanks
and Regards,
Rahul Khengare,
NTT DATA OSS Center, Pune, India.
On Thursday, September 12, 2013 3:54:51 AM UTC+5:30, Forrie wrote:
>
> I've been trying to follow several threads around Google about Puppet and
> it's use (or non-use) of chkconfig on RH Linux.
>
> What prompted me to do this is I noticed that Puppet is, correctly,
> repeatedly logging that it is changing a services from ON to OFF. Funny, I
> thought I had disabled that with:
>
> service { "ip6tables":
> enable => false,
> ensure => stopped,
> }
>
> Which certainly works, but it doesn't disable the service (ie: "chkconfig
> servicename off") -- it seems like there should be a provider that
> correctly integrates with the system "chkconfig" -- I realize that not all
> init scripts honor that, and for that folks can do whatever. This is a
> basic functionality of RH Linux that enables, adds, deletes and otherwise
> alters the levels of basic services. Seems reasonable that Puppet could
> properly interact with it?
>
> We are up to Puppet 3.4.x now. I'm simply asking here as I didn't seem
> to find a definitive answer - a lot of code snippets and suggestions, I
> just wonder if this is on-tap for improvement or if someone has another,
> perhaps clever approach to working with this?
>
>
> Thanks!
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
