Jira (PUP-2664) Support start and stop priorities and runlevels for services

[Stephen Jahl (JIRA)]

Title: Message Title

Stephen Jahl commented on an issue   Re: Support start and stop priorities and runlevels for services I know this is almost moot with the adoption of systemd, but I foresee that I'm still going to have some Debian 7 and Ubuntu 12.04/14.04LTS servers in production for a while. Right now, service init scripts get symlinked into the default locatation (/etc/rc2.d/S20foobar on ubuntu). To work around this, I need to ensure that the S20 symlink is absent, and manage the symlink that has the priority that I want (S99foobar, for example). It would be nice if I could provide start and stop priorities when defining the service like so: service { 'foobar': ensure => running, start_priority => '99' stop_priority => '99' } It looks like the "enable" method doesn't have any parameters, and always calls update-rc.d with "defaults". https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/debian.rb Not sure how scary it would be to add priority parameters there... Add Comment   Puppet / PUP-2664 Support start and stop priorities and runlevels for services 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 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.