On 27/04/14 18:53, Dave Gilbert wrote: > Hi Simon, > 1) Apparently so - I just rebooted the vm to see if I could repeat it, and > it was already stuck at 100% and non-responsive. > (and blueskaj who confirmed it was seeing the same problem on irc) > 2) /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts > --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid > --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf > --cache-size=0 --proxy-dnssec > --enable-dbus=org.freedesktop.NetworkManager.dnsmasq > --conf-dir=/etc/NetworkManager/dnsmasq.d > (typed so typos are probably mine) > > sudo killing the dnsmasq and then reenabling the network interface on nm > gets it working again. >
That's great, thanks. I can't reproduce this, but I have a few hunches as to what the problem may be. If I supply you with modified code are you in a position to compile and test it? Cheers, Simon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1313393 Title: dnsmasq lockup at 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1313393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
