Hello list, I was trying to figure out a way to fix bug 1689551 [1] in a non intrusive way, but so far my best idea involve the creation of a container to hold an ordered and permanent view of /etc/mtab in memory. This list would be updated every time the storage objects are read, and the information would be retrieved from the list instead of directly from /etc/mtab. File systems would be marked ACTIVE and INACTIVE but never removed from the container, to ensure that the index values are persistent and always monotonically increased.
Unfortunately this idea is a bit too intrusive and I'm afraid there's a good chance of breaking something on the way. As I don't have experience with the net-snmp code, I was wondering if I'm missing something and if anyone sees an easier way to fix the problem described in the bug. Also, while reading the code, I found that almost the same concept that I described above is being implemented in mibgroup/hardware/fsys (HAL implementation of FileSystem information), which seems to be work in progress and not yet plugged in the build. Anyone has plans to resume the work started here? I mean, it was not finished due to lack of time and other priorities or the idea was abandoned due to technical issues? [1] https://sourceforge.net/tracker/index.php?func=detail&aid=1689551&group_id=12694&atid=112694 Thanks, Leonardo ------------------------------------------------------------------------------ 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 Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
