Issue #4480 has been updated by Nigel Kersten. Status changed from Needs More Information to Accepted
Thank you for the clarification. It sounds like the commenters in this thread are most equipped to whip up a patch. Is that feasible? ---------------------------------------- Bug #4480: Runit service provider behavior https://projects.puppetlabs.com/issues/4480 Author: Mohit Chawla Status: Accepted Priority: Normal Assignee: Nigel Kersten Category: provider Target version: Affected Puppet version: 0.25.4 Keywords: Branch: When runit provider creates the symlink for a service (to /etc/service), and if service is enabled in the manifest, an error is encountered as: <pre> `notice: Enabling /etc/service/qmail: linking /var/qmail/boot/qmail -> /etc/service/qmail err: //qmail/Service[qmail]/ensure: change from stopped to running failed: Execution of '/usr/bin/sv start /etc/service/qmail' returned 1: warning: /etc/service/qmail: unable to open supervise/ok: file does not exist` </pre> This is because runit needs about 5 seconds to discover new services, but puppet doesn't wait. As far as I can tell, the provider needs to have a provision for delaying the service start by 5 seconds. Not practical really, but that's what I can think of right now. -- 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.
