Bug #58742 for Net-SNMP: Debug data needs a destination other than STDOUT

Wed Jun 23 16:53:23 2010 BitCard [...] ResonatorSoft.org - Ticket created

Subject:

Debug data needs a destination other than STDOUT

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.

Mon Jul 12 22:09:18 2010 dtown [...] cpan.org - Correspondence added 5 min

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?

Mon Jul 12 22:09:18 2010 The RT System itself - Status changed from 'new' to 'open'

Mon Jul 12 22:09:19 2010 dtown [...] cpan.org - Given to DTOWN

Tue Jul 13 16:10:57 2010 BitCard [...] ResonatorSoft.org - Correspondence added

From:

BitCard [...] ResonatorSoft.org

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?

Wed Jul 14 08:46:21 2010 dtown [...] cpan.org - Correspondence added

I will look at possibly adding this to the next release.

Thu Mar 15 10:50:07 2012 dtown [...] cpan.org - Correspondence added 1 min

This request will be addressed when there are enough changes to the Net::SNMP module to warrant a new release.

Thu Mar 15 10:50:13 2012 dtown [...] cpan.org - Status changed from 'open' to 'stalled'