That makes sense, though I would think if you have recurse => true and a subscribe/notify, then checksumming should be enabled by default in that scenario also. It may not be feasible depending on the internal workings of puppet, but that would seem to be the expected behavior.
On Nov 12, 7:20 pm, Luke Kanies <[EMAIL PROTECTED]> wrote: > On Nov 7, 2008, at 1:07 PM, joe wrote: > > > I don't think it's a bug that puppet sees two reasons to bounce the > > service, I think it's a bug that it's only doing it when I change the > > checksum to mtime. The default is md5 (I think) and it would appear > > that when you define a file resource that is a directory with recurse > > => true, puppet should generate md5s on all the files in that dir on > > the first run, so it can keep track of them later, regardless of > > whether puppet is copying the files into that directory or not. It > > seems to only work if puppet is sourcing the files in the directory. > > It should work either way. > > There is no default for checksum. If you use file sources, then the > source parameter makes sure checksums are checked, but otherwise, you > need to add 'checksum => md5' or 'check => checksum' to your resources. > > If you add 'checksum => md5' you'll get the behaviour you want. > > -- > It has recently been discovered that research causes cancer in > labratory rats. > --------------------------------------------------------------------- > Luke Kanies |http://reductivelabs.com|http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
