picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

man: document that [Install] has no effect in unit file .d/*.conf drop-ins

Browse source 
Fixes: #1774
Fixes: #1090
This commit is contained in:
Lennart Poettering 2016-02-10 21:39:36 +01:00
parent 41448597f2
commit be73bb486a
1 changed files with 15 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
man/systemd.unit.xml
View file

@ -178,18 +178,14 @@
directory suffix is <filename>.requires/</filename> in this directory suffix is <filename>.requires/</filename> in this
case.</para> case.</para>
<para>Along with a unit file <filename>foo.service</filename>, a <para>Along with a unit file <filename>foo.service</filename>, a "drop-in" directory
directory <filename>foo.service.d/</filename> may exist. All files <filename>foo.service.d/</filename> may exist. All files with the suffix <literal>.conf</literal> from this
with the suffix <literal>.conf</literal> from this directory will directory will be parsed after the file itself is parsed. This is useful to alter or add configuration settings to
be parsed after the file itself is parsed. This is useful to alter a unit, without having to modify their unit files. Make sure that the file that is included has the appropriate
or add configuration settings to a unit, without having to modify section headers before any directive. Note that for instanced units, this logic will first look for the instance
their unit files. Make sure that the file that is included has the <literal>.d/</literal> subdirectory and read its <literal>.conf</literal> files, followed by the template
appropriate section headers before any directive. Note that, for <literal>.d/</literal> subdirectory and reads its <literal>.conf</literal> files. Also note that settings from the
instanced units, this logic will first look for the instance <literal>[Install]</literal> section are not available in drop-in unit files, and have no effect.</para>
<literal>.d/</literal> subdirectory and read its
<literal>.conf</literal> files, followed by the template
<literal>.d/</literal> subdirectory and reads its
<literal>.conf</literal> files.</para>
<para>In addition to <filename>/etc/systemd/system</filename>, <para>In addition to <filename>/etc/systemd/system</filename>,
the drop-in <literal>.conf</literal> files for system services the drop-in <literal>.conf</literal> files for system services
@ -1093,15 +1089,13 @@
<refsect1> <refsect1>
<title>[Install] Section Options</title> <title>[Install] Section Options</title>
<para>Unit file may include an <literal>[Install]</literal> <para>Unit files may include an <literal>[Install]</literal> section, which carries installation information for
section, which carries installation information for the unit. This the unit. This section is not interpreted by
section is not interpreted by <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> during runtime; it is
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> used by the <command>enable</command> and <command>disable</command> commands of the
during runtime. It is used exclusively by the <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> tool during
<command>enable</command> and <command>disable</command> commands installation of a unit. Note that settings in the <literal>[Install]</literal> section may not appear in
of the <filename>.d/*.conf</filename> unit file drop-ins (see above).</para>
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
tool during installation of a unit:</para>
<variablelist class='unit-directives'> <variablelist class='unit-directives'>
<varlistentry> <varlistentry>