I was hoping I could get a suggestion on how to break up a MIB for an appliance to help in maintenance and code generation via mib2c.
I have a MIB of mixed scalars and tables. Something like this: SystemSettings -- scalars Table1 -- table Table2 -- table TimeSettings -- scalars EmailSettings -- scalars Table3 -- table Currently, I have the entire MIB in one standalone file. This means that I have to run mib2c multiple times with different configs used for each iteration. example: mib2c -c mib2c.scalar.conf myMib mib2c -c mib2c.mfd.conf Table1 mib2c -c mib2c.mfd.conf Does it make more sense to break the MIB apart into seperate files or is there a better way to generate my agent code? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: [EMAIL PROTECTED] Google: [EMAIL PROTECTED] Yahoo: [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
