Am 02/05/2016 um 03:33 PM schrieb Giacomo Mulas: > On Fri, 5 Feb 2016, Michael Biebl wrote: > >> Sorry for the inconvenience. I actually remember (open)resolvconf >> related problems and talked to upstream about that. >> >> Could you test the following upstream commit: >> >> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=af189b3295847cf48bc7616ec3bfc4192458608c >> >> >> >> If that works, I'll upload a new version including that patch. > > Apparently yes. I applied that patch on top of the network-manager debian > source package, I recompiled everything in the src directory, hand > installed > the resulting NetworkManager executable, and it does not segfault anymore.
Ok, thanks for testing. Do you use openresolv or resolvconf? > I still get, in the debug dump, the following: > > NetworkManager[26333]: <debug> [1454681100.518100] > [dns-manager/nm-dns-manager.c > :808] update_dns(): dns-mgr: update-dns: updating resolv.conf > NetworkManager[26333]: <info> dns-mgr: Writing DNS information to > /sbin/resolvc > onf > Failed to try-restart named.service: Unit named.service failed to load: > No such file or directory. > Failed to try-restart unbound.service: Unit unbound.service failed to > load: No s > uch file or directory. > NetworkManager[26333]: <warn> dns-mgr: resolvconf failed with status 3072 > NetworkManager[26333]: <debug> [1454681100.577095] > [dns-manager/nm-dns-manager.c > :549] update_resolv_conf(): dns-mgr: not updating > /var/run/NetworkManager/resolv > .conf since it points to /etc/resolv.conf > NetworkManager[26333]: <warn> dns-mgr: could not commit DNS changes: > resolvconf > failed with status 3072 > However, this is now followed by > > NetworkManager[26333]: <info> (wlan0): Activation: successful, device > activated > > and everything works again. Actually, /etc/resolv.conf, when I open it, > appears correct, as set up by resolvconf in the openresolv package. Perhaps > that is handled by the /etc/network/if-up.d/000resolvconf hook. Afaics that hook is only relevant, if the interface is managed by ifupdown. > > By the way, is it Network-Manager or resolvconf that tries to restart > named.service and unbound.service? That seems to be resolvconf which tries to restart those services. See the scripts in /lib/resolvconf/. Looks like a bug if tries to restart non-exising service In my laptop it can restart > bind9.service, but there is no named.service. Indeed, when I look at > /var/log/syslog, I see that named from the bind9 service is indeed > reloaded, > I guess that happens due to the /etc/network/if-up.d/bind9 hook whenever > an interface is brought up. I believe it's /sbin/resolvconf directly which does it via the hooks in /lib/resolvconf. > So, finally, apparently openresolv already does the right things > whenever an > interface is brought up or down, so NetworkManager should just leave it > alone and all should work? What NetworkManager does, if /sbin/resolvconf is installed, is to push the DNS information to the resolvconf binary and nothing else. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature