I don't know the answer to how long the cache hangs around or how to modify how long it will use the cache but I know that if you run puppet with the --test option it forces puppet to ignore the cache which is a lot less annoying then editing the yaml file. I suppose in the puppet.conf for your clients you could put ignorecache = true and it will always compile the manifest for you. Chris
On Sun, Sep 27, 2009 at 12:50 PM, Tony Maro <tonym...@gmail.com> wrote: > > In my testing, puppet has never caught on to a new config or recipe to > distribute unless I manually delete the node entry from the yaml/nodes > directory. I couldn't find any documentation on how to clear the > cache properly (I stumbled on that method) and I couldn't find any > documentation on how long the cache is kept before it recompiles. All > I saw were references to "stale timestamps" but no real details. I've > waited as long as two days and it just doesn't see the change. > > If one day I decide I need to deploy a new required Gnome key to all > of my Linux desktops, what's the poper method of making sure that the > server realizes all the nodes need to be recompiled? > > I'm using LDAP for storing my node entries, if this makes a > difference. All of my LDAP servers are doing live replication. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
