On 2011-04-21 10:19, Felix Frank wrote:
> I don't think ralsh packs much intelligence in that regard, but relies
> on the redhat provider instead.
Yes, I was thinking "ralsh" as in "ralsh and all the subroutines from
the rest of Puppet that it uses".
> Peaking at the provider, it doesn't appear to do anything special. It
> relies on the default (=init) method to find available services, which
> is browsing /etc/init.d.
>
> I concur that this can possibly be improved. If you do care for good
> chkconfig integration (ralsh has nothing to do with it), you may want to
> consider opening that bug after all ;-)
Right, the 'resources' type of course also uses that functionality. I
didn't think of that. As I said, it already works to do e.g.
service { "rsync": enable => true; }
to enable the xinetd-based rsync service, or
ralsh service rsync
to find out if it is enabled or not. At least in 0.25.5 and 2.6.6. The
'ensure' parameter that ralsh reports isn't in accordance with reality,
though (it seems to be always returning "running")...
/Bellman
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
