On Nov 11, 12:18 pm, David Schmitt <da...@dasz.at> wrote: > As a debianista I obviously haven't touched chkconfig ever. But in the > spirit of DWIM, I would expect a provider to do the magic to get (in > this case) an init-script under the control of the chosen tool.
I'd be happier with that plan if the WIM were less ambiguous. I'm with Bellman in that I would have expected Puppet to issue an error in such cases, so for me, that's part of WIM. I'd be OK with Puppet auto- registering the service with chkconfig, provided that there were a switch to toggle that behavior. Bellman's observation that Puppet's redhat provider changed from using chkconfig's --add / --del modes to using its --on / --off modes makes me want even more to see finer-grained runlevel control. The --add mode, if it does anything, will configure the service to run in whatever are its default runlevels (commonly 345, but sometimes 2345 and occasionally something else). On the other hand, the --on mode without specifying particular runlevels always sets the service to run in levels 2345 (and ignores its run status for other levels). Puppet has no mechanism, with any Service provider, to manage in precisely which runlevels a service will run. This is bad, because there are numerous services that should run in levels 345, but not in level 2. 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 -~----------~----~----~----~------~----~------~--~---
