On Nov 10, 7:20 am, C R Ritson <c.r.rit...@newcastle.ac.uk> wrote: > Fedora 15 uses a mix of init.d and systemd to start services. Our systems > also use NetworkManager. When a client machine is rebooted, NetworkManager is > still initialising (and has sometimes not yet updated /etc/resolv.conf) by > the time puppetd is started. puppetd can then not look up its master server > and end up looping without retrying the name service lookup. How is this best > avoided?
Whichever mechanism F15 uses to start NetworkManager, use the same to start puppet. It should have a way to allow you to set the relative order of NetworkManager and pupptd startup. For example, if NetworkManager is started from an initscript, then start puppetd from an initscript too. Set puppet's start priority lower (larger number) than NetworkManager's. The exact value probably doesn't matter much, because there shouldn't be any other services that depend on puppetd being running. By convention, you should set Puppet's stop priority to 100 - (start priority). John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
