Issue #2712 has been updated by John Bollinger.
Please note that fixing this issue may require more than managing the initscript headers. Initscript headers control the start/stop priorities, but not necessarily the runlevels for which the service is enabled. Here's a summary of relevant chkconfig behaviors in RHEL 5 / CentOS 5 / at least some other RH variants: chkconfig <service> <on | off> => enables / disables the service in runlevels 2, 3, 4, 5; does not manage runlevels 0, 1, or 6 chkconfig --level <levellist> <service> <on | off > => enables / disables the service in the specified runlevels; does not manage other runlevels chkconfig <service> reset => enables / disables the service in all runlevels, according to the chkconfig header in the initscript chkconfig --level <levellist> <service> rest => enables / disables the service in the specified runlevels, according tto the chkconfig header in the initscript In a nutshell, if --level is omitted, then it defaults to 2345 for on / off, and to 0123456 for reset. Example: [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:off 2:off 3:on 4:on 5:on 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig setroubleshoot off [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:off 2:off 3:off 4:off 5:off 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig setroubleshoot on [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:off 2:on 3:on 4:on 5:on 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig setroubleshoot reset [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:off 2:off 3:on 4:on 5:on 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig --level 1 setroubleshoot on [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:on 2:off 3:on 4:on 5:on 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig setroubleshoot reset [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:off 2:off 3:on 4:on 5:on 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig --level 1 setroubleshoot on [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:on 2:off 3:on 4:on 5:on 6:off [jboll...@d100017 am]$ sudo /sbin/chkconfig --level 2345 setroubleshoot reset [jboll...@d100017 am]$ /sbin/chkconfig --list | grep setroubleshoot setroubleshoot 0:off 1:on 2:off 3:on 4:on 5:on 6:off It would be entirely possible -- and to me, preferable -- for the provider to manage a service's runlevels without touching its init script. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
