On Thu, 2008-09-18 at 14:47 +0200, Jan Safranek wrote:
>
> 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.
I think that is a bug in the general case.
I see a couple of different value sources that I think should have
different semantics:
* Command line values - should be preserved for all
reconfigurations
* Config file values - should be rechecked at each SIGHUP, should
be used unless the command line overrides it
* Default values - should be used unless any of the other ones
override it
If a removal from the config file followed by a recheck fails to remove
the value from the actual config then I wonder how one is supposed to
tell the daemon that the value should be turned off?
/MF
-------------------------------------------------------------------------
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
