Issue #2712 has been updated by John Bollinger.
Please note also that there are problems in general with the service.enable property for systems that use runlevels. On those systems the property logically should have an array value, not a scalar value: the service is either enabled or disabled (or not configured) separately for each runlevel. This manifests in some minor weirdness when the redhat provider checks for service enablement via chkconfig, for the result is true if and only if the service is configured to run in the *current* runlevel, whatever that happens to be. The current runlevel in that case will normally be the one that most matters, but the door is open for Puppet to behave surprisingly here. ---------------------------------------- Feature #2712: Support start and stop priorities and runlevels for services http://projects.reductivelabs.com/issues/2712 Author: Robert Foreman Status: Accepted Priority: Normal Assigned to: Category: service Target version: Affected version: 0.25.0 Keywords: Branch: Support start and stop priorities and runlevels for services. 1. For RHEL it would involve managing the chkconfig line in the init script and using chkconfig reset. 2. For Debian/Ubuntu this would be update-rc.d 3. For Solaris/SMF this would be milestones and svcadm 4. For runit this would be runsvchdir and sv -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
