On Tue, Jan 04, 2011 at 09:54:52AM -0800, Wes Hardaker wrote: > You're right it should be optional. And the reasons it was on are > historical: originally the SNMP.xs file was written to be used in > management apps and was later used within snmpd where some of the > "management side things" shouldn't be done.
That's what I guessed. The code in question looked pretty similar to some client-side sample code I found while Googling :-) > You're absolutely right that it shouldn't be done within snmpd. I think > the right way to deal with it is the same way we're doing it in other > apps: if nothing is turned on, *then* turn on stderr. We should be able > to easily test for that. Isn't that already implemented in snmplib? snmp_log_string() calls snmp_enable_stderrlog() if you try to log the first message without any log destinations configured. So it should be safe to just drop the calls to snmp_enable_stderrlog() from perl/SNMP/SNMP.xs and perl/agent/agent.pm, right? Thanks, Martin ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
