Reload config on SIGHUP
lafrech opened this issue · 1 comments
In the current implementation, the config file is read on a regular basis and there is no need to restart the gateway after reconfiguration.
On the other hands, if the file is saved while incomplete or incoherent, the gateway will fail.
It would be more coherent with the other daemons to only reload the config file if SIGHUP is caught.
The downside is that it would require one more action from the user:
sudo service oemgateway reload
I may choose coherence over practicity.
Besides, it may not be obvious to the user that only runtime settings are refreshed, not init settings. If an item (listener, dispatcher) is renamed, it is deleted and recreated, and its in-memory content is lost.
I'm afraid this might become source of trouble in the future.
On the other hand, I appreciate the fact that some parameters can be changed while running (debug level, for instance).