mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-04-26 19:30:39 +02:00
cddb91324c
Previously, if "main.rc-manager" was set to "unmanaged" and "/etc/resolv.conf" was symlink to our internal file "/var/run/NetworkManager/resolv.conf", NM would not rewrite the file, in an attempt to honor the requirement of NetworkManager not changing resolv.conf. No longer special case this. I think it was wrong and inconsistent. If the user specifies rc-manager unmanaged, he also should manage /etc/resolv.conf accordingly. And if the user decided to symlink it to our internal file, that is fine. It should not stop NM from updating that file. Also, this was the only cases, where NM would not write our internal resolv.conf (errors aside). It was inconsitent, and also not documented behavior. Instead, it is documented that `man NetworkManager.conf`: Regardless of this setting, NetworkManager will always write resolv.conf to its runtime state directory /var/run/NetworkManager/resolv.conf. |
||
|---|---|---|
| .. | ||
| nm-dns-dnsmasq.c | ||
| nm-dns-dnsmasq.h | ||
| nm-dns-manager.c | ||
| nm-dns-manager.h | ||
| nm-dns-plugin.c | ||
| nm-dns-plugin.h | ||
| nm-dns-systemd-resolved.c | ||
| nm-dns-systemd-resolved.h | ||
| nm-dns-unbound.c | ||
| nm-dns-unbound.h | ||