Issue #4729 has been reported by Christian Patsch. ---------------------------------------- Bug #4729: YAML Reports - time of creation and permissions http://projects.puppetlabs.com/issues/4729
Author: Christian Patsch Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected version: 2.6.0 Keywords: YAML,log,report Branch: I'm using Puppet 2.6 on a Debian Squeeze Host. After reporting Bug #4501, I digged deeper into YAML Reports. One Thing I encountered quite often is that I don't understand in which case reports are generated or not. Mostly reports are only available if puppet was able to parse all manifests, but even a small typo in a ressource only would generate errors on STDOUT. Is that the desired behaviour in 2.6 including the patch from Bug #4501 ? The more important issue is that reports are written to disk with the file ownerships puppet was called, which will naturally be the root account. Therefore my reports look like this: -rw-r----- 1 root root 7934 Sep 7 17:15 /var/log/puppet/<hostname>/201009071515.yaml The 640 permissions prevent another application from reading the logfiles. As far as I know, logfiles (especially in Debian) normally belong to the group 'adm' - therefore are readable to everyone in the admin group. -rw-r----- 1 root adm 11033 Sep 7 12:31 /var/log/messages Could you please change this to make logfiles more usable ? If any testing or further investigation is required please don't hesitate to contact me. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
