I have this recipe setup to maintain puppetd: service { "puppet": name => $operatingsystem ? { Fedora => "puppet", CentOS => "puppet", Solaris => $kernelrelease ? { "5.10" => "svc:/network/puppetd:default", default => puppetd, }, default => "puppetd", }, ensure => running, enable => true, hasstatus => true, require => [ File["puppet.conf"], Service[network] ], subscribe => File["puppet.conf"], }
If I shut down puppetd on a host (using a Fedora Core 9 host for testing, but has the same problem on Solaris, CentOS and FreeBSD, when I run 'puppetd --test', it does not notice to restart puppet.
Running 'service puppet status' reports: puppetd is stoppedI can add a 'pattern' parameter, but I though since hasstatus is set, that 'service puppet status' should be called instead of doing 'ps - ef|grep puppet'?
I am running puppet 0.24.8 and facter 1.5.4 Ideas? - JimP --- @(#) $Id: dot.signature,v 1.15 2007/12/27 15:06:13 pirzyk Exp $ __o j...@pirzyk.org ------------------------------------------- _'\<,_ (*)/ (*) I'd rather be out biking.
PGP.sig
Description: This is a digitally signed message part