*** This bug is a duplicate of bug 1853164 ***
https://bugs.launchpad.net/bugs/1853164
** This bug has been marked a duplicate of bug 1853164
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1782275
Title:
Conflict between resolvconf and systemd-resolved dhclient scripts
Status in
This issue is still present in Ubuntu focal.
Here is what I see that needs to happen:
systemd: The /etc/dhcp/dhclient-enter-hooks.d/resolved script should be
renamed to something like 00resolved or aaa_resolved, so that other
packages that install scripts into that directory will have their
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1782275
Title:
Conflict between resolvconf and systemd-resolved dhclient scripts
Status
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
This issue can be addressed with a manual action, but first you have to
dig into the scripts to diagnose the problem, and really if resolvconf
is installed then it should just work.
Part of this setup involves disabling systemd-resolved, in favor of a
"direct" /etc/resolv.conf, to match the
Given that it is a conffile, you can remove the one you do not need.
Why do you want to use resolvconf, instead of resolved? I was expecting
for people to have /etc/resolv.conf to point at either
/run/systemd/resolve/stub-resolv.conf or
/run/systemd/resolve/resolv.conf (as needed) and have
8 matches
Mail list logo