>>>>> On Mon, 19 Sep 2011 11:28:56 -0700 (PDT), sujata patra >>>>> <sujata_patra2...@yahoo.com> said:
sp> If because of netsnmp_daemonize() , engineID changes, is it possible sp> to keep the engineID same after fork too ? You definitely need to have the right engineID in use. Make sure that /var/net-snmp/APPNAME.conf is writable by your application so it can save the engine ID. But because the snmpd.conf file may have a different engineID (and should) you can't copy the usmUser line from it to the abc-demo.conf file and have it work unless you make the engineID the same (which you shouldn't do). Instead, stop the abc-demo, add this to your abc-demo.conf file, and then start it again: createUser myuser MD5 abcd1234 Which will create the user with the abc-demo's engine ID. You shouldn't need to specify the engineID on the snmpwalk command line either, because it'll auto-detect it and synchronize with it. [I'm refraining on discussing the security implementations of engineID discovery here] -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
