Issue #6523 has been updated by Ben Hughes. Status changed from Unreviewed to Accepted
---------------------------------------- Bug #6523: verbose and debug options always force console log destination https://projects.puppetlabs.com/issues/6523 Author: donavan m Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Some applications, particularly agent, force `Puppet::Util::Log.newdestination(:console)` if `options[:debug]` or `options[:verbose]` are set. This is regardless of, and in addition to, any user options set via '--logdest'. This leads to duplicate messages if the user specified destination also writes to STDOUT. It also makes it impossible for a user to 'silently' run some applications without catching STDOUT. The handling of log destinations seems a bit haphazard in the applications. The apply & inspect applications work as I'd expect, processing --logdest then setting the default with `Puppet::Util::Log.newdestination(:console) unless options[:logset]`. Others, like agent queue & application.rb always force `newdestination(:console)` when (IMHO) unrelated options like loglevels are set. See http://groups.google.com/group/puppet-dev/browse_thread/thread/42c0aa7cede250c9 -- 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.
