Hi all, I have a tidy block set up to clean up old Puppet reports (older than 1 month). One side effect of this is that every file that is removed gets added into the state.yaml file. On a small scale this is not a bad thing - it keeps track of what's been culled, etc...
On a larger scale (ie. Tidy is cleaning a lot of files with different filenames) the state.yaml file will grow and grow. This whole state file is read in on a regular basis by the Puppet daemon. Its probably a small one for most people, but in theory it is a persistent memory leak. What is the general best practice for managing Puppet state/config databases? Greg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
