On 7 July 2011 08:41, Giuseppe Modugno <g.modu...@elettronika.it> wrote: > It seems the only method to avoid loading MIBs is to set MIBDIRS variable to > ""
No - that will still try to load the MIB files, but the SNMP library doesn't know where to find them (hence the errors that you are seeing). If you really don't want to load the MIB files, then try setting the MIBS environment variable - or equivalents. Try something like: export MIBS=""; snmptrap -v2c -c public 192.168.1.1 "" 1.3.6.1.4.1.... MIBS="" snmptrap -v2c -c public 192.168.1.1 "" 1.3.6.1.4.1.... snmptrap -m "" -v2c -c public 192.168.1.1 "" 1.3.6.1.4.1.... all of which will avoid loading the MIB files, but in a cleaner manner. Dave ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
