3 ms·
> My major complaint against systemd is that its documentation is so complete, it becomes quite dense and you have to understand quite a lot of interconnected p
by tetha 3y ago
> My major complaint against systemd is that its documentation is so complete, it becomes quite dense and you have to understand quite a lot of interconnected parts. "The problem is the problem" though, its complex because what it aims to do is complex. I am still positive on it as a whole though.
Aye, that is a problem. We have like 3-4 recipes in our internal documentation of "Here are the 12 lines of systemd for each of the 9 things you need to do to solve 90% of your use cases". I might ask around if we could put this onto some public blog or something.
- bravetraveler 3y agoDiscoverability is such a thing. For example, which of these do I want?: man systemd.{exec,unit,service} It's not too bad to get a general feel for what's possible, but recalling where is frustrating. These three are so closely related they're notable. Others, like timers, are a little more obvious. I've settled on Ansible roles. I define the important bits and config mgmt does the rest
- Bu9818 3y agosystemd.directives(7) is useful if you know what directive you want to read about but not in what manual it's in.
- bravetraveler 3y agoAwesome, thank you! :D