On 9 August 2012 10:44, Stuart Kendrick <skend...@fhcrc.org> wrote: > So now I'm poking through the pre-converted list of MIB files running > hexdump, looking for end-of-line characters ... and all I'm seeing is > '0a', which suggests that the MIB files I'm reading were all Unix-style. > > Would you identify a particular MIB file as being full of 0a0d line > termination?
All five of the files that you posted have this format. Though I suppose this might be a consequence of having passed through the mail system. Looks like this was a red herring. Sorry. > [I've updated the files at https://vishnu.fhcrc.org/add_mibdir] I've tried using these versions instead, and that's helped pinpoint the problem. If you look in the IETF folder, you should see five duplicate names (four of the form T11-FC*, plus DOCS-IETF-SUBMGT-MIB) In fact, the names aren't exact duplicates - there is actually a space at the end of the second version. This space is what is confusing the MIB indexing. If you rename the 10 MIB files in the IETF folder that end in a space (or delete the duplicates), and the 22 in the Cisco folder (which are all apparently duplicates) - then I'm reasonably confident that things should start working again. Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
