The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #6523

verbose and debug options always force console log destination

Added by donavan m about 5 years ago. Updated over 4 years ago.

Status:AcceptedStart date:03/01/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

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

History

#1 Updated by Ben Hughes about 5 years ago

  • Status changed from Unreviewed to Accepted

Also available in: Atom PDF