Had a reply from Simon Kelly (upstream). The worry is about race conditions and reading /etc/hosts or resolv.conf after the 'mtime' has been changed, but before the file has been completely written out (dnsmasq already tries to backoff and schedule a re-read a couple of seconds late if it finds an incomplete file). The preferred solution is for the process modifying the appropriate file to manually send:
sudo killall -HUP dnsmasq to the process. Currently (on Ubuntu) dnsmasq is run as uid='nobody', so these needs elevated privileges (which are needed anyway for editing those files). This is okay for a human, but is less automatic than the previous situation where /etc/hosts was being watched. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946754 Title: dnsmasq does not respect/watch '/etc/hosts' updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/946754/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
