Thank you again for your interesting explanations. If I want to give a quickly answer to the client, it is better that the info stay in the MIB stored. I have just to consult a value with snmpget and not to interroge in that moment the underlying subsystem. I implement an Agent to fulfil the NTCPI specification (urban traffic). I search the way to implement the NTCIP1201-2004 and NTCIP1202-2004 and NTCIP8004-A-2004 MIBs. I would happily use snmpset to fill with the traffic signs information. The problem is with the variables read-only, ... I can not use snmpset. Can I in some way "jump" this limitation? Do you understand what I mean? I don't really see what is the utility of table_tdata, table iterator in my case, which process invoke this functions?
-----Mensaje original----- De: Dave Shield [mailto:[email protected]] Enviado el: lunes, 30 de marzo de 2009 13:54 Para: Gómez González, Enrique CC: [email protected] Asunto: Re: I obtain that with make install 2009/3/30 "Gómez González, Enrique" <[email protected]>: > I try to execute the examples, data_set, delayed_instance, etc > Each time I modify something I must launch configure, make clean, make and > make install? If you are changing the *name* of the code file containing your MIB module, then yes - you should run make clean configure make make install If you are using the same filename for your MIB module, then it's not necessary to run "configure" every time (and you can probably get away without "make clean"). > I want to modify the value of a variable of a MIB each second That's probably not the best way to handle this. A more typical approach would be to wait until you receive a query and then interrogate the underlying subsystem (e.g. a temperature probe) to retrieve the current value. Don't think of the MIB architecture as a "database" that needs to be kept up to date. It's actually more of an interface specification, that allows the two sides a common way of referring to particular items of information. The remote client doesn't care *how* the agent finds out the data it's asked for - just as long as it gets a sensible answer. If you're modelling a frequently-changing dataset, then I wouldn't use the data_set framework. But I have a dislike of that particular helper anyway - I find it somewhat cumbersome to use. It's really designed for a relatively static dataset, which is mostly configured and updated via SNMP SET requests. If you're modelling some other externally-changing data set, then I'd personally choose one of the other helpers. Probably either the table_data (i.e. tdata) or iterate mib2c templates. Dave
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
