Even if systemd is spawning another of its own processes, it's still systems which is doing the resolving. Just get my system running, and log errors....
Agreed, and that (along with Lee D's comments, especially destroying loose coupling) is one of many reasons I detest systemd.
But the apparently common misconceptions about how systemd works must be avoided else you look just as stupid as many of the systemd evangelists.
The (predictable) downvotes to my previous comment, ironically, illustrate the exact reason for making that comment in the first place.
Biting the hand that feeds IT
