[Resolvconf-devel] Bug#847440: resolvconf: run resolvconf service before any networking service

Ryan Harper ryan.harper at canonical.com
Thu Dec 8 09:34:27 UTC 2016

Package: resolvconf
Version: 1.79.1
Severity: normal
Tags: patch
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,

When using other networking services (networkd, NetworkManager) instead of
networking, resolvconf doesn't run early enough to ensure it's watching for
DNS changes.  

In Ubuntu, the attached patch was applied to achieve the following:

Instead of encoding each networking service name in the service unit file use 
network-pre.target to ensure resolvconf runs before any other networking

  * debian/resolvconf.service: resolvconf service must run before any of the
  possible network configuration services (ifupdown, networkd, NetworkManager)
  so use network-pre.target instead of service names. (LP: #1636912)

Thanks for considering the patch.

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-51-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: resolvconf_1.79.1.debdiff
Type: text/x-diff
Size: 493 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20161208/28d5eb42/attachment.diff>

More information about the Resolvconf-devel mailing list