Hi,
I have this:
service { "bind9":
ensure => running,
hasrestart => true,
pattern => "named",
require => Package["bind9"],
}
because the process is called 'named'.
Best regards,
Martijn Grendelman
On 31-08-11 22:56, Russell Van Tassell wrote:
Just a couple odd questions... does the status return 0 or 1 when bind is
running? If the process table is used, would you need a "name" parameter to
differentiate the name versus the process name? And, what version of puppet?
You might need a "hasstatus" in there, as well?
Ref: http://docs.puppet
On Aug 31, 2011, at 1:47 PM, David Nalley wrote:
> On Wed, Aug 31, 2011 at 4:43 PM, Craig White wrote:
>> Seems that every cycle, puppet thinks that bind9 service is stopped and
>> wants to restart...
>>
>> info: Applying configuration version '1314822598'
>> notice: /Stage[main]/Bind::Service
On Aug 31, 2011, at 1:55 PM, Steven VanDevender wrote:
> Craig White writes:
>> Seems that every cycle, puppet thinks that bind9 service is stopped and
>> wants to restart...
>>
>> info: Applying configuration version '1314822598'
>> notice: /Stage[main]/Bind::Service/Service[bind9]/ensure: ens
Craig White writes:
> Seems that every cycle, puppet thinks that bind9 service is stopped and
> wants to restart...
>
> info: Applying configuration version '1314822598'
> notice: /Stage[main]/Bind::Service/Service[bind9]/ensure: ensure changed
> 'stopped' to 'running'
> notice: Finished
On Wed, Aug 31, 2011 at 4:43 PM, Craig White wrote:
> Seems that every cycle, puppet thinks that bind9 service is stopped and wants
> to restart...
>
> info: Applying configuration version '1314822598'
> notice: /Stage[main]/Bind::Service/Service[bind9]/ensure: ensure changed
> 'stopped' to 'run
Seems that every cycle, puppet thinks that bind9 service is stopped and wants
to restart...
info: Applying configuration version '1314822598'
notice: /Stage[main]/Bind::Service/Service[bind9]/ensure: ensure changed
'stopped' to 'running'
notice: Finished catalog run in 3.70 seconds
But it's run
