Zhouhuai Shen wrote: > Hi Jan, > > I checked the patch for 'v1trapaddress', it used the following to > register the v1trapaddress string in the snmpd.conf: > > netsnmp_ds_register_config(ASN_OCTET_STR, app, "v1trapaddress", > NETSNMP_DS_APPLICATION_ID, NETSNMP_DS_AGENT_TRAP_ADDR); > > Once the snmpd is re-read as it receives a SIGHUP signal, the string > v1trapaddress will not be refreshed. For example, if I manually > remove the 'v1trapaddress 10.0.0.1' from the snmpd.conf, then a > SIGHUP is sent, the snmp daemon still thinks that the string defined > for v1trapaddress is there
v1trapaddress does react to SIGHUP, it you change it, then the agent's address in outgoing traps will be different. On the other side, you are right with the removal - the old value is still used even if it's removed from the config file. That's the usual behavior of snmpd, it does not restore default value if a config option gets deleted. I am not sure if it is bug or feature. Jan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
