Maybe interesting things to note: 1. When in bad state: - The mentioned ENV var change in /etc/default/dnsmasq and `sudo systemctl restart dnsmasq` immediately resolves the issue 2. When in good state: - Commenting out the ENV var and running `sudo systemctl restart dnsmasq` does not immediately re-cause the issue - After a reboot, the bad state can be observed again (systemd-resolved using 100% of a CPU core)
Maybe there is an order of operations thing here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
