On 04/21/2011 09:35 AM, Thomas Bellman wrote: > On 2011-04-21 09:18, Felix Frank wrote: > >> So obviously, there is no xinetd provider. I concur that such a thing >> would probably be worthwile. If your Ruby is good (or if you like doing >> new things ;-), you may want to cobble one together yourself as a >> plugin, it's not rocket science. > > Well, on RedHat:ish systems, the chkconfig(8) command can manage xinetd > services, and since Puppet has a "redhat" provider which uses chkconfig, > it is already possible to manage xinetd services using the Puppet, at > least on RedHat systems. > > However, puppet resource/ralsh doesn't seem to understand the xinetd > portion of the output from 'chkconfig --list', so it doesn't show > those services. At least, I *guess* ralsh uses 'chkconfig --list' to > find out which services exist on the system, but I haven't checked. > This should probably be reported as a bug by someone who cares about > ralsh (i.e., not me).
Hi, I don't think ralsh packs much intelligence in that regard, but relies on the redhat provider instead. 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 ;-) Also, thanks for the useful hint about xinetd+chkconfig, I wasn't aware of that. Cheers, Felix -- 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.
