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?
Chris Ritson (Computing Officer and School Safety Officer) Room 707, Claremont Tower, EMAIL: c.r.rit...@ncl.ac.uk School of Computing Science, PHONE: +44 191 222 8175 Newcastle University, FAX : +44 191 222 8232 Newcastle upon Tyne, UK NE1 7RU. WEB : http://www.cs.ncl.ac.uk/ -- 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.
