On Thu, Jan 06, 2011 at 08:23:14AM -0800, Wes Hardaker wrote: > Err... I think you're right. It should probably be checked. Can you > delete it and try using the modules in both in-and-out of the agent?
Sorry for the late reply, I only now found time to test this properly. So here are the results: I dropped the calls to snmp_enable_stderrlog() both from SNMP.xs and agent.pm, though the latter never seemed to get called during my tests. Messages still end up on stderr when using SNMP.xs outside the agent and the agent now successfully closes stderr unless you give the -Le option. The only drawback is that you get an additional "No log handling enabled - using stderr logging" message when the first log message is printed. But that matches the behaviour of e.g. snmpwalk, so I guess that's OK. Are there other opinions? Thanks, Martin ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
