Thanks for your answer
I tried your option, but the result is similar.
I have saw the log file of "snmp master agentx" and its traces are:
register_mib: unregistering SNMPv2-SMI::transmission.12346.700.1.0
register_mib: unload(SNMPv2-SMI::transmission.12346.700.1.0, [NIL])
register_mib: unregistering SNMPv2-SMI::transmission.12346.700.1.0
register_mib: unregister_mibs_by_session(0x8136900) ctxt ""
register_mib: unload(SNMPv2-SMI::transmission.12346.700.2.0, [NIL])
I'm seeing the log file and it seem that the oid
"SNMPv2-SMI::transmission.12346.700.1.0" is unregistered twice. To
unregistered OID's, I use "netsnmp_unregister_handler(myReg)"
What it is happening, because the application is returning a segmentation
fault?
Thanks
2011/11/10 Dave Shield <[email protected]>
> On 10 November 2011 16:23, francisco moreno <[email protected]> wrote:
>
> > I have made a similar application as "subagent" example of net-snmp.
> > I trying register and unregister seven oids several times. The problem is
> > when I unregister the oids.
> > I think that my method is wrong:
> >
> > REGISTER OID
> > --------------------------
> > netsnmp_handler_registration *myreg;
> :
> > netsnmp_register_watched_instance(myreg, watchInfo);
>
>
> If you are using the handler-based registration APIs,
> then you probably need to use the handler-based
> unregistration call as well.
>
>
> > UNREGISTER OID
> > --------------------------------
> > unregister_mib(oid_name, TAM_OID);
>
>
> Try using
>
> netsnmp_unregister_handler( myreg );
>
> Dave
>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
