Hello List, I'm running puppet on OS X Tiger 10.4.11. When using the launchd plist to start up puppet, I'm frequently seeing this issue where launchd will start up puppet very early in the boot process, often before configd can set the hostname on the client. This results in cert requests for "localhost" on the puppetmaster, and the clients aren't able to communicate until puppetd is restarted on the client, at which point it uses the correct name and works fine. To get around this, I have switched to using a systemstarter script to start puppet so that it runs late enough not to cause this problem. Is there a way to configure launchd (or puppet) to work around this? I don't see any way to set dependancies or ordering of processes with launchd but perhaps I am missing something. Has anyone else experienced this?
Thanks, Daniel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
