News for hackers. Stuff that matters.
Re:Systemd needs official documentation on best practices by pmoriarty on Friday November 08, 2019 @03:13PM (#21486219)
The lack of clear, thorough, reliable documentation is one of my biggest gripes with systemd.
Re:Systemd needs official documentation on best practices by beefhash on Friday November 08, 2019 @03:17PM (#21486253)
The man pages that ship with systemd seem very thorough to me. The problem is rather that they're very thorough in the first place. They're a very hard, lengthy read and you kind of require to understand all of it before things begin to make sense.
Re:Systemd needs official documentation on best practices by bashinator on Friday November 08, 2019 @04:18PM (#21486902)
That's exactly the point the article is making. In addition to the comprehensive documentation, systemd users need best practices for a good range of common-to-uncommon use cases.
Re:Systemd needs official documentation on best practices by goatinaboat on Friday November 08, 2019 @04:07PM (#21486770)
Agreed, what’s lacking is documentation on how the many, many options can interact with each other.

Today I wanted to get systemctl list-unit-files give me the full path to each file. Couldn’t figure it out.