mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-27 04:03:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

man: correct/tweak text about unit name syntax

Browse Source 
Unit names can be 255 characters long, not 256.

We first say "name prefix" and then continue with "unit prefix".
Confusing. Couldn't figure out which term is better hence settled on
"unit name prefix".
This commit is contained in:
Lennart Poettering 2023-03-28 23:25:52 +02:00 committed by Luca Boccassi
parent 3a051522ce
commit 75f7e5e547
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
man/systemd.unit.xml
View File

@ -110,19 +110,19 @@
<para>Unit files are loaded from a set of paths determined during compilation, described in the next <para>Unit files are loaded from a set of paths determined during compilation, described in the next
section.</para> section.</para>
<para>Valid unit names consist of a "name prefix" and a dot and a suffix specifying the unit type. The <para>Valid unit names consist of a "unit name prefix", and a suffix specifying the unit type which
"unit prefix" must consist of one or more valid characters (ASCII letters, digits, <literal>:</literal>, begins with a dot. The "unit name prefix" must consist of one or more valid characters (ASCII letters,
<literal>-</literal>, <literal>_</literal>, <literal>.</literal>, and <literal>\</literal>). The total digits, <literal>:</literal>, <literal>-</literal>, <literal>_</literal>, <literal>.</literal>, and
length of the unit name including the suffix must not exceed 256 characters. The type suffix must be one <literal>\</literal>). The total length of the unit name including the suffix must not exceed 255
of <literal>.service</literal>, <literal>.socket</literal>, <literal>.device</literal>, characters. The unit type suffix must be one of <literal>.service</literal>, <literal>.socket</literal>,
<literal>.mount</literal>, <literal>.automount</literal>, <literal>.swap</literal>, <literal>.device</literal>, <literal>.mount</literal>, <literal>.automount</literal>,
<literal>.target</literal>, <literal>.path</literal>, <literal>.timer</literal>, <literal>.swap</literal>, <literal>.target</literal>, <literal>.path</literal>,
<literal>.slice</literal>, or <literal>.scope</literal>.</para> <literal>.timer</literal>, <literal>.slice</literal>, or <literal>.scope</literal>.</para>
<para>Units names can be parameterized by a single argument called the "instance name". The unit is then <para>Unit names can be parameterized by a single argument called the "instance name". The unit is then
constructed based on a "template file" which serves as the definition of multiple services or other constructed based on a "template file" which serves as the definition of multiple services or other
units. A template unit must have a single <literal>@</literal> at the end of the name (right before the units. A template unit must have a single <literal>@</literal> at the end of the unit name prefix (right
type suffix). The name of the full unit is formed by inserting the instance name between before the type suffix). The name of the full unit is formed by inserting the instance name between
<literal>@</literal> and the unit type suffix. In the unit file itself, the instance parameter may be <literal>@</literal> and the unit type suffix. In the unit file itself, the instance parameter may be
referred to using <literal>%i</literal> and other specifiers, see below.</para> referred to using <literal>%i</literal> and other specifiers, see below.</para>