projects / systemd / .git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c40bd28) | patch
man: add a note that resolvconf updates /etc/resolv.conf in specific circumstances
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Sun, 19 Apr 2020 20:01:21 +0000 (22:01 +0200)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Sun, 19 Apr 2020 20:01:21 +0000 (22:01 +0200)
commit924ccc35f95cabbcb475a659f4a2e2f4cd9ff7c6
tree0754f4b93c3b5f422bf93e7bd4e1755f0bb053edtree | snapshot
parentc40bd28419ca02718360d016c47f4ac5495ed0eacommit | diff
man: add a note that resolvconf updates /etc/resolv.conf in specific circumstances

When someone knows how the whole ecosystem works, this is understandable.
But for someone coming from a system where resolvconf updates /etc/resolv.conf
directly, this can be rather surprising.

For https://bugzilla.redhat.com/show_bug.cgi?id=1815605.
man/resolvectl.xml diff | blob | history
https://github.com/systemd/systemd.git