On May 28, 11:17 am, Luke Bigum <luke.bi...@lmax.com> wrote: > Hi all, > > Does anyone have an all-in-one-run work around for this issue: > > http://projects.puppetlabs.com/issues/791 > > Where Puppet / Ruby / libc is not rereading the naming service settings > if Puppet itself changes them. I've got a situation where we set up LDAP > but can't create some files as an LDAP user in the same run.
The bottom line is that any given process will read nsswitch.conf at most once. It is important to understand that if you are running the agent in daemon mode, because then *every* run between service start and service shutdown on any given node is performed by the same process (that reads nsswitch.conf at most once, even if one of the runs changes it). Therefore, if you are managing nsswitch.conf then you should probably run the Puppet agent periodically via cron instead of as a long- running daemon. Moreover, name-service lookups performed by the agent will never recognize changes to the name service configuration performed during the same run. > Hacky answers are welcome - my objective is to as close to a single pass > as possible, I really don't want to have to wait for another scheduled run. If you run the agent from cron then you could conceivably simulate a multiple-stage Puppet run by making the command be something such as puppet agent --onetime --tag name_service && puppet agent --onetime 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.
