From: SourceForge.net <no...@so...> - 2010-01-29 03:30:38
|
Bugs item #2941983, was opened at 2010-01-28 19:30 Message generated for change (Tracker Item Submitted) made by fenner You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112694&aid=2941983&group_id=12694 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: agent Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bill Fenner (fenner) Assigned to: Nobody/Anonymous (nobody) Summary: trapsess in snmpd.conf can cause stderr logging to turn on Initial Comment: In net-snmp 5.5, but probably in earlier versions too, an snmpd.conf line such as trapsess -v 3 -u trapdusr -l authPriv -Ci -a SHA -3k a3fbc81cbc5ffc7ee449efdb9587b3665a248d0c -x AES -3K e3bc7d9db5a1fb382e3a743f743d67e010317a08 1.2.3.4:5678 causes stderr logging to be turned on, even if snmpd was launched with arguments such as -Lf /dev/null -LS0-6d This is because trapsess uses the common snmp_parse_args() handler to parse the trapsess line, and if snmp_parse_args() doesn't see an -L option, it calls snmp_enable_stderrlog() to turn on stderr logging. This causes snmpd to fail to close fd's 0, 1 and 2 (even though it's still going into the background); this foils a system that waits for EOF from a popen()'d "/usr/sbin/snmpd" to learn that snmpd has successfully launched. A workaround is to repeat one of the logging options, such as -Lf /dev/null, on each trapsess line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112694&aid=2941983&group_id=12694 |