Disabling systemd-resolved breaks dhclient resolvconf integration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
To reproduce, mask resolved:
sudo systemctl mask systemd-
...then disable network-manager for ifupdown interfaces:
$cat /etc/NetworkMan
[main]
plugins=
dns=default
rc-manager=
[ifupdown]
managed=false
[device]
wifi.scan-
...and reboot.
You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/
This is because /etc/dhcp/
The file existence check in the beginning of /etc/dhcp/
-if [ -x /lib/systemd/
+if [ -x /lib/systemd/
Arguably, /etc/dhcp/
tags: | added: id-5acd885138c94c5bb1f96431 |
tags: | added: resolved-resolvconf |
tags: | added: ddstreet |
The hasty push to replace resolvconf with resolved is having disastrous consequences. User experience and system stability should be valued over forced migration to an unproven, poorly tested, and in many cases unwanted new system.
Name resolution is one of the fundamental building blocks of a networked system. I don't understand the eagerness to change it so quickly. It almost seems careless. One might argue that all of systemd has been pushed on the user in a like manner, but I won't go there...at least it's not upstart.