Issue #11361 has been updated by Nigel Kersten.
I'd really rather not make this configurable. We have too many config options that are very very rarely used, and the cost of maintaining them means we spend less time working on more important bugs and features I believe. Given we have good support for logging to a syslog facility, this seems like the sort of thing that is best supported by defining the relative priority levels in your syslog listener for different log files, don't you think? ---------------------------------------- Bug #11361: Every time you stop puppetd, an info report is sent https://projects.puppetlabs.com/issues/11361 Author: Jo Rhett Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: logging Target version: Affected Puppet version: 2.6.12 Keywords: Branch: Every time you stop puppetd, you get an info-level report Tue Dec 13 03:34:07 +0000 2011 Puppet (notice): Caught TERM; calling stop I don't think this is particularly useful information such that it needs a report for it. If it is report-worthy, why not puppet startup? -- 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.
