Issue #6697 has been updated by Thomas Hatch.
No, there are not, the rc script component that starts all of the services is a for loop with 2 if statements that iterates over the DAEMONS array in the rc.conf. So editing the /etc/rc.conf and adding in the service name is the same as chkconfig httpd on. So I probably should not have compared it to a BSD runlevel process, it only follows it in philosophy. So it would be viable if we appended the service names to the end of the DAEMONS array in the rc.conf with the ordering based on the require statements in the services, but I don't know how viable that would be within the puppet code. So the problem is that Arch does not set up the start up ordering of the services for you, it makes the user to do it. ---------------------------------------- Bug #6697: Repair default init script path on Arch Linux https://projects.puppetlabs.com/issues/6697 Author: Thomas Hatch Status: Needs More Information Priority: Normal Assignee: Thomas Hatch Category: service Target version: Affected Puppet version: Keywords: Branch: Arch Linux uses a BSD style init, and the init scripts are located in /etc/rc.d rather than /etc/init.d This means that when running an Arch puppetmaster, a stanza setting the default service path var to /etc/rc.d is required in the site.pp It would be nice if on Arch systems the default service path var was automatically set to /etc/rc.d -- 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.
