On Thu, Feb 4, 2010 at 11:39 PM, Eric Sorenson <ahp...@gmail.com> wrote:
> > On Feb 4, 2010, at 9:29 PM, Dan Bode wrote: > > Question 2: I also noticed that sometimes I have to run it twice to get >> all the changes through. That might be because of errors in the manifests, >> but I've seen that happen also when everything should be fine. >> Is there a reason for this? >> > > this should never be required. Possibly you are not using the > require/before/notify/subscribe metaparameters to specify the correct > ordering? > > > Wellll.... not "never", right? > never = almost never. > If you have added tools that a provider needs to enable itself (say, the > 'gem' executable) , puppet won't pick it up until its next initialisation. > I've also seen ldap dependencies not get picked up immediately after > binding, so for instance creating user directories which auto-require that > user to exist will fail until the next run. > this is true > The first one might be addressable with some introspection, like a > metaparameter to signal puppet to re-initialise without exiting, the second > one looks pretty much like a race condition that one could probably sleep() > around in an exec. > I hadnt considered cases where your dependencies have to sync with an external source. > -=Eric > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.