Thanks, Dave. This is very helpful to understand these two files. What happens in my test is that, when re-config is set, the agent snmpd read the snmpd.conf, not the snmp.local.conf. So I think it is the snmpd.conf that controls the agent's behavior. This is what I mean re-config the agent.
About my requirement in this situation, surely I could modify this snmpd.conf. But I don't know what is the snmp.local.conf used for in net-snmp package. Could you give me some hints, Dave? Thank you very much. BR/vivid 2010/5/26 Dave Shield <[email protected]> > On 26 May 2010 13:06, Weiwei Zhang <[email protected]> wrote: > > What is the difference between snmpd.conf and snmp.local.conf? > > There are actually two different questions here: > > 1) what is the difference between {xxx}.conf and {xxx}.local.conf ? > The answer is "nothing". > The config parsing code looks for files with *both* of these names > (for any given application token), in a range of locations. > The idea here is to support both common configuration (identical > across a range of machines), and system-specific configuration. > > For example, you could put the access control settings in 'snmpd.conf' > (so they are consistent across all systems), while having > sysLocation > in 'snmpd.local.conf' (so it's different for each system) > > > 2) what is the difference between snmp.conf and snmpd.conf ? > > The first contains library-level config (typically used for > client-side tools, > snmpget, snmpwalk and the like). > The second is specific to the SNMP agent (snmpd). > > See 'snmp.conf(5)' and 'snmpd.conf(5)' for details. > > Dave > -- --- Best Regards Weiwei Zhang
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
