#1119: command line option --trace does not provide backtrace
------------------------+---------------------------------------------------
Reporter: jtimberman | Owner: community
Type: defect | Status: new
Priority: normal | Milestone:
Component: client | Version: 0.24.2
Severity: normal | Resolution:
Keywords: trace | Stage: Unreviewed
Patch: None | Complexity: Unknown
------------------------+---------------------------------------------------
Comment (by jtimberman):
Does running the server in trace mode cause more messages to be logged for
clients connecting that aren't running --trace? We use a log analysis
system that mails interesting logs to the team, so additional logging
could be annoying.
Is there a possibility of having trace enabled at the client side, perhaps
as an additional feature?
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1119#comment:2>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
