read the man pages. type “man systemd” into a linux terminal, and when finished also read the “see also” pages at the bottom. man systemd.unit is also a “central” page, it says lots of things common to all unit file types.
when you stumble into long parameter lists, you can skip them, you probably won’t use most of them. not because they are useless, though, so it’s better to at least read the names of all the parameters you come across that way so you have a picture what’s available.
skip systemd.directives, but know what it is: a catalogue of all systemd directives with the man page they are documented at. very useful, when you want to find something specific.
“man systemd.special” is special, it’s more about its internals, very informational, but relies on preexisting knowledge
read the man pages. type “man systemd” into a linux terminal, and when finished also read the “see also” pages at the bottom. man systemd.unit is also a “central” page, it says lots of things common to all unit file types.
when you stumble into long parameter lists, you can skip them, you probably won’t use most of them. not because they are useless, though, so it’s better to at least read the names of all the parameters you come across that way so you have a picture what’s available.
skip systemd.directives, but know what it is: a catalogue of all systemd directives with the man page they are documented at. very useful, when you want to find something specific.
“man systemd.special” is special, it’s more about its internals, very informational, but relies on preexisting knowledge