On 14.5.2012 14:53, jcbollinger wrote: > On May 12, 11:09 am, Markus Falb <markus.f...@fasel.at> wrote: >> I have a class irqbalance with a service defined and it does not work as >> expected and thats why I am asking for advice. >> >> service { 'irqbalance': >> ensure => running, >> enable => true, >> require => Package['irqbalance'], >> >> } >> >> $ puppetd --test >> does start the service (expected) >> >> $ puppetd --test --tags irqbalance >> *does not* start the service (unexpected) >> why is this? > > > Prior to Puppet 2.7, if a Service resource does not have "hasstatus => > true" then Puppet will check its status by looking for its name in the > process table. (In Puppet 2.7 the default for this parameter changed, > so you need to explicitly set hasstatus => false to get the table > lookup behavior.) > > I speculate that you are running something older than 2.7 (so probably > 2.6.x), and that when Puppet scans the process table to check whether > irqbalance is running, it matches on your Puppet command line "puppetd > --test --tags irqbalance".
Uh. I read about that change but I was not clear about the consequences. This would mean that looking in the process table is unreliable and now I am thinking about setting a default Service { hasstatus => true } so I do not have to specify it for every service. Thanks -- Kind Regards, Markus Falb
signature.asc
Description: OpenPGP digital signature