Skip Menu |
 
rt.cpan.org will be shut down on March 1st, 2021.

This queue is for tickets about the Net-SNMP CPAN distribution.

Report information
The Basics
Id: 58742
Status: stalled
Worked: 6 min
Priority: 0/
Queue: Net-SNMP

People
Owner: dtown [...] cpan.org
Requestors: BitCard [...] ResonatorSoft.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: v6.0.0
Fixed in: (no value)



Subject: Debug data needs a destination other than STDOUT
Download (untitled) / with headers
text/plain 472b
The current DEBUG_INFO sub just prints the data out on standard out. However, this debug information could be output into a filehandle, similar to the DBI->trace method. Closing and opening STDOUT is a workaround, but this redirects ALL STDOUT traffic, which isn't what I wanted. This could be implemented as a second parameter on the debug method. Support for filehandles is preferred (or both) over a filename parameter, so that PerlIO::via filehandle support works.
Download (untitled) / with headers
text/plain 261b
The debug output was made available so that I, as the author, could troubleshoot the Net::SNMP module and was not expected to be consumed by the typical user. Is there a specific application or reason for you to collect the debug output other than from STDOUT?
From: BitCard [...] ResonatorSoft.org
Download (untitled) / with headers
text/plain 962b
It can be useful to troubleshoot things on the packet level, since it can spit out packet dumps, as well as give a step-by-step breakdown of what is happening. I've only had to use it a few times, but it's still helpful. As far as the logging, since most of what I write is web tools, having the debug data spit out on the production web server as raw text isn't ideal. If it can be redirected to a log, I can log the data, do some requests, and look at the log. I have a Perl::via module that puts in the timestamps and all of that (similar to your standard syslog). Again, I have a similar setup for DBI requests when I use that module. On Mon Jul 12 22:09:18 2010, DTOWN wrote: Show quoted text
> The debug output was made available so that I, as the author, could > troubleshoot the Net::SNMP module and was not expected to be consumed by > the typical user. > > Is there a specific application or reason for you to collect the debug > output other than from STDOUT?
I will look at possibly adding this to the next release.
Download (untitled) / with headers
text/plain 110b
This request will be addressed when there are enough changes to the Net::SNMP module to warrant a new release.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.