On Nov 10, 10:13 am, Thomas Bellman <bell...@nsc.liu.se> wrote:
> The problem is that 'chkconfig <service> on' does an implicit add of
> the service; but it does a half-assed job, in that it only adds the
> start links, not the kill links. Thus, it is very easy to get into
> the broken state by doing a 'chkconfig --del <service>', followed by
> 'chkconfig <service> on'. I get exactly that behaviour for e.g.
> the puppetmaster service when I try. I didn't expect that.
Why did you have any particular expectation for that scenario at all,
though? I agree that chkconfig has some quality-of-implementation
issues, but the bottom line is that it has no documented behavior for
the scenario you describe. If you want predictable, stable results
then you should stick to the documented behaviors of your tools.
Layering higher-level tools such as Puppet on top does make it harder
to tell whether you are exercising only documented behaviors. It is
implicit in Puppet's Service type that it manages a service that is
already correctly installed, but perhaps it would be better if the
docs were explicit about that. What constitutes a "correctly
installed" service varies by Provider, unfortunately, but it would be
well to add those details to the various Providers' descriptions.
Following the principle of exercising only documented behavior, I
think Puppet's "redhat" service provider should recognize only those
services reported by chkconfig --list. That would prevent Puppet from
causing a misconfiguration by turning on a service not already managed
by chkconfig. If an ability to register a service with chkconfig is
needed (not clear to me that it is), then that should be controlled by
a separate parameter.
It would be lovely if Service supported specifying the particular
runlevels in which a Service should be enabled, and in that context it
would make sense for Puppet to ensure that the service was disabled in
all other runlevels. The existing "enable" property could be used for
that: the "true" and "false" values now defined for it would retain
their meanings, but a digit string (e.g. "345") would specify that the
service should be enabled in those runlevels and disabled in all
others.
And for what it's worth, I never use chkconfig --del unless I'm
removing the service from the system altogether. If for some reason I
need to leave a service on the system that must never automatically
run, then I chkconfig --level 0123456 <service> off. YMMV.
John
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
