Re: sysObjectID still returns an incorrect value

2010-09-22 Thread Wes Hardaker
> On Wed, 22 Sep 2010 10:37:39 -0400, Fulko Hew said: FH> I just tested rc3... and I give that release/patch _my_ blessing. Thanks for the positive feedback! FH> Now it would be nice If I could also get my other two patches FH> incorporated that prevent net-SNMP from core dumping under cert

Re: sysObjectID still returns an incorrect value

2010-09-22 Thread Fulko Hew
On Mon, Sep 20, 2010 at 8:22 PM, Wes Hardaker < [email protected]> wrote: > > On Thu, 16 Sep 2010 12:41:38 -0400, Fulko Hew > said: > > FH> Are there any other scenarios that I missed testing? > > FYI, I applied your patch to the trunk today. > Great! I just tested rc3... and I

Re: sysObjectID still returns an incorrect value

2010-09-20 Thread Wes Hardaker
> On Thu, 16 Sep 2010 12:41:38 -0400, Fulko Hew said: FH> Are there any other scenarios that I missed testing? FYI, I applied your patch to the trunk today. -- Wes Hardaker Please mail all replies to [email protected]

Re: sysObjectID still returns an incorrect value

2010-09-16 Thread Fulko Hew
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 > said: > > FH> WATCHER_MAX_SIZE | WATCHER_SIZE_IS_PTR | WATCHER_SIZE_UNIT_OIDS, > > FH> whereas the value passed in via sysObjectIDByteLength has already

Re: sysObjectID still returns an incorrect value

2010-09-16 Thread Wes Hardaker
> On Wed, 15 Sep 2010 16:00:42 -0400, Fulko Hew 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>

Re: sysObjectID still returns an incorrect value

2010-09-15 Thread Fulko Hew
On Wed, Sep 15, 2010 at 2:52 PM, Fulko Hew wrote: > As long as I was testing 5.6.rc2, I thought I'd test it to > see if the 'sysObjectID is truncated' issue was resolved. > > What I see is that the value is now returned as padded with zeros. > I.e. > > 1.3.6.1.2.1.1.2.0: > 1.3.6.1.4.1.8072.3.2.10

Re: sysObjectID

2006-02-08 Thread Dave Shield
On Tue, 2006-02-07 at 14:05 -0800, Fong Tsui wrote: > Does sysObjectID need to be top OID of MIB of the system? No. > My original .1.3.6.1.2.1.1.2 == .1.3.6.1.4.1.XXX.2 > The all MIB of the system is under .1.3.6.1.4.1.XXX.2 Is this from a vendor-supplied agent? The standard Net-SNMP configurat

Re: sysObjectID

2006-02-07 Thread Thomas Anders
Fong Tsui wrote: Now if I change .1.3.6.1.2.1.1.2 == .1.3.6.1.4.1.XXX.2.1.3.3.2. All other MIB stays the same. Will it be a problem? Not that I'm aware of. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --- This SF.net email