+++ This bug was initially created as a clone of Bug #888271 +++
Investigation of [bug 847289] showed snmpd is not careful about dynamic
modules when it comes to reloading the configuration (such as upon
Dynamic modules seems to be loaded anew, which may corrupt previous
instances, avoid a proper cleanup actions and the like.
As per Jan Safranek, there is a room for improvement and less
--- Additional comment from Jan Safranek on 2012-12-18 07:32:15 EST ---
snmpd should not call init_<modulename> when the module is already loaded.
This implies that snmpd never reloads modules and the only way to update a module is to restart snmpd.
Sorry for the noise, I came to the conclusion the current behavior is
OK and the limitation + solution are known .
Unless there is another issue with the current state, I would prefer
it as a status quo (maybe a sanity check at other dynamic modules we
provide should be performed -- generally, unregister registered MIBs
and registered alarms in deinit_<module> function).