On Tue, 2005-10-11 at 11:58 -0400, Robert Story wrote: > On Mon, 10 Oct 2005 15:20:25 +0100 Dave wrote:
> DS> How about > DS> > DS> /var/net-snmp/mib-index.1 (2, 3, 4 ...) > DS> > DS> each file containing the name of the MIB directory concerned, > DS> followed by the list of MIB file/module mappings. > > And for non-root users? Then the index files simply wouldn't be updated, and the MIB directory would be parsed afresh each time. Note that if the agent is run as root, then it would typically update the mib-index files when it starts up. Non-root users would be able to use those files OK. Another possibility would be to *look* for a .index file in each directory (and use it if present and up-to-date), but not to create it automatically. Instead, there could be an explicit command (or option to an existing command), which could be used to generate a suitable .index file for a specified MIB directory. > DS> The other "something better" that has occasionally been suggested, > DS> is switching everything to use the libSMI MIB handling. > > As in requiring that it is installed, or importing the code into > our code base? Both options have issues... Either. I *know* there are issue involved - I'm just flagging it as a possibility. Dave ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
