On 17/10/06, Roland Stigge <[EMAIL PROTECTED]> wrote:
> Yes, moving the indexes to a separate location like /var/lib/snmp is a
> reasonable compromise. A good, documented way for using multiple mibs
> locations would be nice.
You mean something like:
$ man snmp.conf
[snip]
mibdirs (mib-dirs|+mib-dirs)
Look for textual MIBs to parse in the list of ':'
separated directories. If the
directive value starts with a '+' it prepends this list
to the front of the default
directory list compiled into the application. Note that
this value can be overridden
by the MIBDIRS environment variable.
>
> BTW: Using index files (and therefore potentially regenerating them)
> raises the issue of respective local permissions. Everyone running
> programs using the lib must have write permissions to the index files,
> while other non-authorized users maybe shouldn't. Is this currently
> handled appropriately?
Yes.
If the person running the program doesn't have write access to the
index file, then the code to regenerate this file will simply fail
silently. The library will still build up the list of MIB file ->
MIB module mappings, but will just hold this in memory, and won't be
able to save it for future re-use. So the index file will remain out
of date, and further runs of this (or other) applications will
continue to ignore it.
When an authorized user (i.e. with write access) finally runs the
same command, then the index file *will* be updated and then be
available for all users (both privileged and not).
Dave
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
