On Oct 6, 2010, at 6:06 AM, Bruce Richardson wrote: > One of the nice features of using the Tidy resource to prune a directory > hierarchy in puppet is that any File resources you create within that > tree will not be touched. However, the tidy resource *will* log that it > is tidying them. This is not good. I like puppet to log any changes it > makes so that logwatch can pick them up - puppet should only need to > make changes if the state of the node is not as described. > Unfortunately, with the Tidy logging as it is, where I want to tidy any > files not managed by puppet I either have to set the loglevel for the > tidy resource so that it doesn't log *anything* or suffer spurious log > messages and explicitly filter them out on the logwatch side. > > I think it would be reasonable of puppet not to log the tidying of files > which are not actually tidied. Do people agree? In which case I'll > file a bug report. Or have I missed a clean way of resolving this?
I didn't quite understand what you said. I hope this general rule helps: If puppet is logging something about a resource every run AND not changing anything AND not failing, I think you should file a bug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
