>>>>> On Thu, 24 Dec 2009 15:49:12 -0200, Leonardo Chiquitto >>>>> <[email protected]> said:
LC> File systems would be marked ACTIVE and INACTIVE but never removed LC> from the container, to ensure that the index values are persistent LC> and always monotonically increased. LC> Unfortunately this idea is a bit too intrusive and I'm afraid there's LC> a good chance of breaking something on the way. As I don't have LC> experience with the net-snmp code, I was wondering if I'm missing LC> something and if anyone sees an easier way to fix the problem LC> described in the bug. That's probably the only real choice and is similar (I think) to what's happening now for interfaces. It's the only way to keep track of consistent indexing. LC> Also, while reading the code, I found that almost the same concept LC> that I described above is being implemented in mibgroup/hardware/fsys LC> (HAL implementation of FileSystem information), which seems to be work LC> in progress and not yet plugged in the build. Anyone has plans to LC> resume the work started here? I mean, it was not finished due to lack LC> of time and other priorities or the idea was abandoned due to LC> technical issues? Dave Shield was working on that; You might ask him for his status of it. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
