On Wed, Apr 20, 2011 at 10:42:21AM -0700, Tim Coote wrote:
> [I'm using the training machine from puppetlabs]
> puppet resource service xinetd
Which one? Not all of them use xinetd. Certainly the CentOS 5 machine I
have doesn't have xinetd. So it won't report it as a service. Querying it
directly will say not to run it as it doesn't exist.
[ben@centos56:~]% puppet resource package xinetd
package { 'xinetd':
ensure => 'absent',
}
[ben@centos56:~]% puppet resource service xinetd
service { 'xinetd':
ensure => 'running',
enable => 'false',
}
I don't know if Fedora uses xinetd by default as I don't have a Fedora
machine here to test with I'm afraid.
> From a design perspective, I'd expect such an
> interface to explicitly tell me what it cannot recover, rather than
> silently not returning it, as I've no way of knowing that there's a
> constraint on the o/s / distro vs a bug in puppet.
I think this may, to a degree, be a case of not being able to know the
unknown. Certainly resource can improve in some areas though.
If it is a bug then I'd like to get it fixed too.
--
Ben Hughes || http://www.puppetlabs.com/
--
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.
