On Mon, Feb 20, 2012 at 12:00 PM, Khoury Brazil <khoury.bra...@gmail.com> wrote: > Hi, > > Starting a new thread since the question and problem are completely > different at this point. I've written modules that implement a client > side firewall and overwrite and flush any changes made by a user. This > is mandated by several different internal security policies and of > course compliance. I'm pretty much at the stage where I'm ready to > start deploying but recently hit a snag: catalog expiration on the > client. The client caches and uses the cached catalog as expected, but > unfortunately if a client is "off-network" for too long the catalog > expires and we get fun stuff like: > > Not using expired catalog for <hostname> from cache; expired at <date> > > I've tried using 'use_cached_catalog' just as a test, but it appears > that an expiration date in a catalog takes priority over everything > else.
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: run puppet agent through cron instead of running a daemon. configure runinterval to a much longer period. 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.
