search for: pam_limits_d

Hi, For a long time now when we run puppetd --test I get the following double output on our custom facts, info: Retrieving plugin info: Loading facts in scratch info: Loading facts in os_name info: Loading facts in pam_limits_d info: Loading facts in os_platform info: Loading facts in nvidia_graphics info: Loading facts in hostname_hour info: Loading facts in os_version info: Loading facts in rhn info: Loading facts in scratch info: Loading facts in os_name info: Loading facts in pam_limits_d info: Loading facts in os_pla...

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?