Control: clone -1 Control: reassign -1 openresolv Control: retitle -1 restarting non-existing services leads to failure Control: found -1 3.7.2-1
Am 02/05/2016 um 07:00 PM schrieb Michael Biebl: > Am 02/05/2016 um 06:26 PM schrieb Giacomo Mulas: >> well, apparently either resolvconf does not work properly or NetworkManager >> does not call it as it expects to be called, since it fails (from the debug >> output of NetworkManager): >> NetworkManager[26333]: <warn> dns-mgr: resolvconf failed with status 3072 >> NetworkManager[26333]: <debug> [1454681100.577095] So, I looked into this a bit more. What NM does is, it opens a pipe to /sbin/resolvconf, and then pushes the DNS information to that process. You can simulate that by creating a tmp file and doing this by hand: $ cat /tmp/dns # test search test nameserver 192.168.179.1 $ cat /tmp/dns | /sbin/resolvconf -a NetworkManager Failed to try-restart nscd.service: Unit nscd.service failed to load: No such file or directory. Failed to try-restart unbound.service: Unit unbound.service failed to load: No such file or directory. $ echo $? 6 $ cat /etc/resolv.conf # Generated by resolvconf search test nameserver 192.168.179.1 As you can see, resolvconf returns a non-zero exit code, even though it apparently has properly updated /etc/resolv.conf That non-zero exit code is generated afaics, because resolvconf tries to restart non-existing services and propagates that error to the caller. It should handle that more carefully. This is a bug in openresolv. I'm therefor cloning this bug report and reassign it to openresolv. The second bug is, that NetworkManager didn't handle that failure (non-zero exit code) properly and segfaulted because of that. This is fixed by the already mentioned patch. I'll upload a fixed package this evening. Regards, Michael -- 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