Can you give me a link to that documenation and tooling? Because every time I go to troubleshoot an issue, I end up in a tangled mess of trying to figure out how systemd and NetworkManager have decided to configure themselves on this particular system, and I give up.
I don’t know how it happens, but I can set up Ubuntu on a dozen laptops in exactly the same way, and a week later they all have different configurations.
Can you give me a link to that documenation and tooling?
Linux daemons and utilities typically come with manuals that get installed alongside the software. There’s a command line tool, aptly called man, that can be used to search and display these manuals. So for instance, man resolvectl displays the manual for the command line utility that you can use to control, configure, monitor and debug the systemd-resolved daemon. (Although I usually look up the man page online because it’s more convenient to scroll through than in a terminal.) Man pages for a given daemon will typically mention near the bottom related man pages for e.g. control utilities like resolvectl, so it’s not necessary to remember it by heart.
a week later they all have different configurations.
I’m trying to remember any situation where one of the systemd components would change its configuration on its own, but I’m coming up blank. It may be my memory failing me, but possibly that’s the wrong tree to bark up?
Unix grey beard here.
Yes. Distros with systemd are simply easier to maintain.
Even when DNS resolution isn’t working properly?
Especially then. Great documentation and support tooling make troubleshooting much easier.
Can you give me a link to that documenation and tooling? Because every time I go to troubleshoot an issue, I end up in a tangled mess of trying to figure out how systemd and NetworkManager have decided to configure themselves on this particular system, and I give up.
I don’t know how it happens, but I can set up Ubuntu on a dozen laptops in exactly the same way, and a week later they all have different configurations.
Linux daemons and utilities typically come with manuals that get installed alongside the software. There’s a command line tool, aptly called
man, that can be used to search and display these manuals. So for instance,man resolvectldisplays the manual for the command line utility that you can use to control, configure, monitor and debug thesystemd-resolveddaemon. (Although I usually look up the man page online because it’s more convenient to scroll through than in a terminal.) Man pages for a given daemon will typically mention near the bottom related man pages for e.g. control utilities likeresolvectl, so it’s not necessary to remember it by heart.I’m trying to remember any situation where one of the systemd components would change its configuration on its own, but I’m coming up blank. It may be my memory failing me, but possibly that’s the wrong tree to bark up?
Arch wiki ftw
Never had a systemd caused DNS issue.
Then I must be using it wrong. I kept systemd-resolved on my laptop but on my desktop I use plain old
/etc/resolv.conf