Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dnsmasq: reload configuration by signal #1601

Closed

Conversation

feckert
Copy link
Contributor

@feckert feckert commented Dec 22, 2017

  • If the system name was changed then the "dnsmasq" must be restarted to rewrite his config with the new hostname. Adding "/etc/config/system" to the reload trigger will trigger "dnsmasq" on "/etc/config/system" change.

  • To apply the new configuration "dnsmasq" must get restarted with start/stop to rewrite the configuration and then also restart a new instance to serve the new configuration. If reload_service was triggered then only sending a signal to dnsmasq to reload his config for the running service is enough. No new instance is required to serve the new configuration.

I have added this functionality one year ago, but this introduce errors on service reload and was reverted.
ADD:
TDT-AG@854459a#diff-f65b4391dc02a776f873f8e933742458
REVERT:
TDT-AG@93227e4#diff-f65b4391dc02a776f873f8e933742458

If the hostname in /etc/config/system is modified the dnsmasq should also
get triggered to rewrite/reload the config.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Send a signal with procd for dnsmasq if service should reread his config.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
@dedeckeh dedeckeh closed this Dec 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants