On Wed, 25 Feb 2015 16:03:34 -0000 Tim wrote: TC> I have created a subagent using the mib2c tool and the TC> mib2c.mfc.conf file. TC> TC> This gives me support for monitoring a single table. TC> TC> However, my subagent will need to monitor different types of TC> data and they will be stored in different tables. TC> TC> The mib2c tool produces a bunch of c files like: TC> TC> <tablename>_data_access.* TC> <tablename>_data_get.* TC> <tablename>_interface.* TC> TC> Etc. TC> TC> What I'm tinking of doing is to copy all these files and update TC> them so that they refer to my second table, i.e. using the TC> second table name. Naturally the oids and the table structure TC> would need updating in the header files. TC> TC> Then I can initialize both tables in my subagent main function. TC> TC> Does this seem like a reasonable proposal? Seems pointless in TC> reinventing the wheel in order to get support for additional TC> tables, why not use the existing source and modify it. TC> TC> Of course, if there is a better way I'd be happy to hear it.
I suppose you could do it that way, but I'm not sure why you would want to manually copy and replace functionality, instead of simply running mib2c for each table. Robert ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
