Dave Shield wrote:
[...]OK - then the cache helper is an ideal solution for you. That's pretty much what this does.
It will load your data the first time that a query arrives (*not* when the agent starts up), and will release and re-load it whenever another request arrives, and the cached data is "too old" to be useful. You can specify how long "too old" is.
If you're running an "snmpwalk" command (and the cache timeout is chosen sensibly), then this will probably all be serviced by a single load. That contrasts with loading the table within the get_{first,next} hooks, where it will typically be reloaded for *each* value individually.
The main documentation for this helper is at
http://www.net-snmp.org/dev/agent/group__cache__handler.html
There isn't an example, I'm afraid. (At least not yet....)
This method seem to be good. I can use it with Iterator ? (get_next..., get_first).
Without example, it will be difficult so :(
Many thanks.
------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
