Issue #2712 has been updated by Robert Foreman.
Unfortunately no, the chkconfig command does not override the init script. chkconfig uses the commented lines at the head of the init script to determine the appropriate run levels, start and stop priorities. We would need to manage this line from the sysv init script for the service followed by a chkconfig reset: # chkconfig: 2345 20 80 (start levels, start priority, stop priority) For Ubuntu it looks like we would have to use update-rc.d or manage the symlinks directly. They are using upstart, but they are still using a sysv compatibility package. It looks like RHEL is also moving toward upstart, but I don't know what that will mean for chkconfig yet. I am primarily interested in managing the start/stop order, but in order to adequately manage start/stop priorities I think we would have to include levels. ---------------------------------------- Feature #2712: Add start/stop order for services http://projects.reductivelabs.com/issues/2712 Author: Robert Foreman Status: Needs more information Priority: Normal Assigned to: Category: service Target version: Affected version: 0.25.0 Keywords: Branch: For RHEL it would involve managing the chkconfig line in the init script and using chkconfig reset. Not sure about other platforms. -- 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 -~----------~----~----~----~------~----~------~--~---
