Issue #11395 has been updated by Jo Rhett.
I will say that I don't actually have a specific target in mind, so if you come up with a better solution I'm all ears -- but the following comments come to mind: 1. Having two levels -- info and verbose -- do exactly the same thing is obviously not useful. 2. Having output from something with loglevel 'verbose' show up when you do something with --verbose makes an awful lot of sense. 3. Right now, changing a file resource's loglevel to verbose creates the effect that changes to the file don't show up in tagmail, but do show up in "puppet agent --verbose" which seems to make sense to my mind. Process behaves differently. ---------------------------------------- Bug #11395: Loglevel doesn't work on processes https://projects.puppetlabs.com/issues/11395 Author: Jo Rhett Status: Needs More Information Priority: Normal Assignee: Category: logging Target version: Affected Puppet version: 2.6.12 Keywords: Branch: It is incredibly common that we update /etc/nagios/nrpe.cfg and restart the nrpe daemon. So much so that we really don't want to know every time it happens (500+ emails from tagmail) I was able to remove the notification that nrpe.cfg had changed by setting LogLevel to verbose, but we still receive notification that the nrpe process was restarted. I tried putting loglevel on that too, but it has no effect. -- 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.
