On Mon, Feb 20, 2012 at 12:32 PM, Khoury Brazil <khoury.bra...@gmail.com> wrote: > On Mon, Feb 20, 2012 at 12:07 PM, Nan Liu <n...@puppetlabs.com> wrote: >> I think you've already stumbled on the answer in the previous thread. >> The cache timeout is unfortunately tied to runinterval setting. I'm >> pretty sure there's a ticket requesting to split them up. The closest >> thing you can do today: > > Is there any way I can add my support to that ticket?
+1 and watch the ticket, and of course I can't find the ticket # in redmine at the moment. >> run puppet agent through cron instead of running a daemon. >> configure runinterval to a much longer period. > > Thanks Nan. A few more questions, if you don't mind: > What's the effect of the runinterval on the expiration date? If I set > the runinterval to 14 days, can I then expect a cached catalog to > expire 14 days after compiled? Does the catalog expiration affect how > often it pulls a new compiled catalog from the puppet master? For > example: If node01 has a cached catalog that was compiled on > 02/23/2012, expires on 03/08/2012 and the client is back on the > network with the puppet master again on 02/26/2012 does the client > pull a new catalog that would then expire on 03/11/2012? Catalog expiration does not affect pulling new catalogs, just how long it takes to expire. The behavior you described matches what I saw last time when I tried this. Thanks, Nan -- 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.
