> OK - I think I've tracked down the problem. > > These index files seem to use DOS-style line endings (i.e. CR/LF) > Unfortunately, the code to process them includes some very Unix-centric > thinking, and is explicitly looking for the LF character. > (See 'snmplib/parse.c:add_mibdir()') > > I'm only surprised that this hasn't bitten us before, since that code > has been there since forever! > > Dave OK, so I've run dos2unix on every MIB file ... and I see the same results.
[I've updated the files at https://vishnu.fhcrc.org/add_mibdir] 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? --sk ------------------------------------------------------------------------------ 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 [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
