On Wed, 16 Mar 2011 17:25:51 +0200 Timo wrote: TT> > I think the concept you are talking about for the cache is ok, but I'm not TT> > sure that auto-sychronized is the right name. It's more of a keep-alive, isn't TT> > it? simply bumping the expiration time when the cache is used? TT> TT> Correct. The flag name is misleading. I first thought that it'd do more TT> things, but all it had to do is bump the timestamp on each GET. So if TT> you have a good new name, I can run sed and post a new patch.
How about NETSNMP_CACHE_RESET_TIMER_ON_USE? Please add a note in the documentation that using this flag without a method of keeping the cache fresh will result in stale data if polling is more frequent than the expiration timer. TT> Correct. The kernel sends deletion events, which in turn are sent as arp TT> entry updates containing NETSNMP_ACCESS_ARP_ENTRY_FLAG_DELETE. So it is TT> fully synchronized. TT> [...] TT> As you see, it's now split to arp_common, arp_netlink and arp_linux. The TT> arp_linux side basically keeps the old behaviour. Great. That alleviates my concerns. Thanks. Robert ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
