Re: sysObjectID still returns an incorrect value
Fulko Hew <[email protected]>
| Newsgroups | gmane.network.net-snmp.devel,gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Sep 16, 2010 at 12:31 PM, Wes Hardaker < [email protected]> wrote: > >>>>> On Wed, 15 Sep 2010 16:00:42 -0400, Fulko Hew <[email protected]> > said: > > FH> WATCHER_MAX_SIZE | WATCHER_SIZE_IS_PTR | WATCHER_SIZE_UNIT_OIDS, > > FH> whereas the value passed in via sysObjectIDByteLength has already been > FH> converted > FH> into bytes. so the above statement on line 339 > FH> should instead be: > > FH> WATCHER_MAX_SIZE | WATCHER_SIZE_IS_PTR > > Thanks for diving into the code to look at that. I started to yesterday > but got distracted. After making the above change does it fix your > problem? > Yes, It did for me. I tested: 1/ Net-SNMP reporting its 'internally' defined sysObjectID 2/ a sysObjectID override in the snmpd.conf file. Are there any other scenarios that I missed testing? ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders