Hey there, Check your cron with crontab -l and you'll see a line that calls "/opt/puppet/sbin/refresh-mcollective-metadata" every 15 minutes. That's the process that updates the facts.yaml file with your current custom facts. You can trigger it whenever you'd like :)
On Thu, Feb 16, 2012 at 3:19 PM, Tony C <[email protected]> wrote: > I'm not sure if this is the right group or not, but i'll start here. > > I have Puppet enterprise 2.0, playing around with custom facts. > > I have noticed that adding a custom fact to any module will distribute > that fact to all machines, regardless if they are assigned to that > module or not. Is there a way around this, or is this just by design? > > I have the pluginsync and mcollective setup to use /etc/puppetlabs/ > mcollective/facts.yaml. > > server.cfg > # Facts > factsource = yaml > plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml > > Without doing anything, after a few minutes, my facts.yaml gets > populated with the new custom fact, even without following this guide: > > > http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML > > > and mco find -F myfact will work as well, not at first, but after a > minute or 2. why is that? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Gary Larizza Professional Services Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
