On 12/3/10 5:13 PM, Nigel Kersten wrote:
> On Fri, Dec 3, 2010 at 11:58 AM, Derek Yarnell <[email protected]> wrote:
>> So we run puppetd as a long running ruby process on the hosts. When we
>> update a fact that gets auto sync'd to the host it seems when puppetd wakes
>> up and starts its catalog run it doesn't re-sync the facts. It you run it
>> standalone it will or if you restart the service then it will do the right
>> thing. Do other people see this? Or have you all gone to running out of
>> cron?
>
> What puppet version?
>
> Are you using factsync or pluginsync?
Hi,
I have noticed this through 0.24.x, 0.25.x and now 2.6.1 which we are
running (both server and client) now everywhere.
pluginsync = true
pluginsource = puppet://$server/plugins
Thanks,
derek
--
---
Derek T. Yarnell
University of Maryland
Institute for Advanced Computer Studies
--
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.
