Issue #9623 has been updated by eric sorenson. Status changed from Needs Decision to Code Insufficient Assignee changed from eric sorenson to Johan Huysmans
I think we'd take a patch to the chkconfig provider that did this all the time automatically; it's just enforcing intent. I don't see benefit in exposing this in the DSL -- i.e. what would be the use case where you would want NOT to enforce chkconfig listed priority? ---------------------------------------- Feature #9623: service does not manage start/stop priority https://projects.puppetlabs.com/issues/9623#change-67130 Author: Johan Huysmans Status: Code Insufficient Priority: Normal Assignee: Johan Huysmans Category: service Target version: Affected Puppet version: 2.6.7 Keywords: Branch: In the init script you can mention the start/stop priority. # chkconfig: 2345 55 25 But the service resource only knows if it is on or off. It should be useful if this is automatically checked. chkconfig has the resetpriorities option which does this. Currently I implemented it manually: service { "funcd": ensure => running, enable => true, require => File["/etc/rc.d/init.d/funcd"]; } file { "/etc/rc.d/init.d/funcd": owner => "root", group => "root", mode => 0755, source => "puppet:///func/funcd.init", notify => Exec["chkconfig_funcd_resetpriorities"]; } exec { "chkconfig_funcd_resetpriorities": refreshonly => true, command => "/sbin/chkconfig funcd resetpriorities"; } -- 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://projects.puppetlabs.com/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.
