shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-24 21:34:08 +03:00
Code

man: document that generators can generate instances+templates and regular unit files (#7342)

Browse Source 
This addition is kept brief on purpose, since in order to write a good
generator users don't really need to grok templating/instantiation.

Fixes: #7257
This commit is contained in:
Lennart Poettering 2017-11-16 03:37:25 +01:00 committed by Yu Watanabe
parent d38802e881
commit 7655cd3d58
1 changed files with 12 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
man/systemd.generator.xml
View File

@ -74,17 +74,14 @@
<refsect1> <refsect1>
<title>Description</title> <title>Description</title>
<para>Generators are small binaries that live in <para>Generators are small executables that live in <filename>&systemgeneratordir;/</filename> and other
<filename>&usergeneratordir;/</filename> and other directories directories listed above.
listed above. <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> will execute those
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> binaries very early at bootup and at configuration reload time — before unit files are loaded. Generators may
will execute those binaries very early at bootup and at dynamically generate unit files (regular ones, instances as well as templates) and unit file
configuration reload time — before unit files are loaded. <filename>.d/</filename> drop-ins, or create symbolic links to unit files to add additional dependencies or
Generators can dynamically generate unit files or create symbolic instantiate existing templates, thus extending or overriding existing definitions. Their main purpose is to convert
links to unit files to add additional dependencies, thus extending configuration files that are not native unit files dynamically into native unit files.</para>
or overriding existing definitions. Their main purpose is to
convert configuration files that are not native unit files
dynamically into native unit files.</para>
<para>Generators are loaded from a set of paths determined during <para>Generators are loaded from a set of paths determined during
compilation, as listed above. System and user generators are loaded compilation, as listed above. System and user generators are loaded
@ -189,13 +186,10 @@
<listitem> <listitem>
<para> <para>
Generators should only be used to generate unit files, not Generators should only be used to generate unit files and symlinks to them, not any other kind of
any other kind of configuration. Due to the lifecycle configuration. Due to the lifecycle logic mentioned above, generators are not a good fit to generate
logic mentioned above, generators are not a good fit to dynamic configuration for other services. If you need to generate dynamic configuration for other services,
generate dynamic configuration for other services. If you do so in normal services you order before the service in question.
need to generate dynamic configuration for other services,
do so in normal services you order before the service in
question.
</para> </para>
</listitem> </listitem>