>>>>> Guy Harris writes:
Guy> Well, there's one other issue, which I may not have mentioned
Guy> before:
Guy> At one point you'd sent me an "smi.conf" file to get libsmi to
Guy> load all the relevant MIBs; I'd prefer not to require that, as
Guy> part of the process of installing Ethereal, the user have to edit
Guy> a libsmi configuration file.
Guy> I'm not sure Ethereal should supply its own configuration file,
Guy> either, as it doesn't know what MIBs libsmi offers to load.
Guy> Is there some way to tell libsmi "load all the MIBs"?
libsmi does not really know what "all the MIBs" means unless you write
it down in libsmi.conf. :-)
In general, the smi.conf mechanism is just a fallback for applications
that do not maintain their own configuration files. On the other hand,
the smi.conf mechanism is very nice if you have several applications
that need MIB information and there is a single place to configure
them all if you add a new MIB.
As I said before, loading "all the MIBs" is just wasting resources and
not very useful. I think the default behaviour should be to load "the
most common IETF MIBs", which is probably just a list of ten MIBs.
Perhaps libsmi should install itself with such a list of default MIBs
in the system wide smi.conf file.
/js
--
Juergen Schoenwaelder Technical University Braunschweig
<schoenw@xxxxxxxxxxxxxxx> Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
