Stop and start modules on configuration reload ?

[mohierf]

On a configuration reload, the modules are stopped and started. Currently, this is of no interest if the reload happens because the arbiter backend module detected some modifications in the configuration ... perharps we should discuss about this for some improvements ?

[fpeyre]

Maybe just reload the module if their configuration change ? Or could be depend of how the module works ?

[mohierf]

Perharps only sending the new configuration to the modules would be enough. The parent daemon should not stop the module if it is still prenset in the new received configuration