shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-01-05 09:17:44 +03:00
Code

man: document that "systemctl mask" doesn't work for units whose file is in /etc

Browse Source 
Fixes: #27965
(cherry picked from commit 3122f4d752)
(cherry picked from commit cc13c367f2)
(cherry picked from commit 1ca95101f9)
This commit is contained in:
Lennart Poettering 2023-06-08 16:59:15 +02:00 committed by Luca Boccassi
parent f7f08e4943
commit bd60251c8f
1 changed files with 18 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
man/systemctl.xml
View File

@ -941,13 +941,24 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
<term><command>mask <replaceable>UNIT</replaceable>…</command></term>
<listitem>
<para>Mask one or more units, as specified on the command line. This will link these unit files to
<filename>/dev/null</filename>, making it impossible to start them. This is a stronger version of
<command>disable</command>, since it prohibits all kinds of activation of the unit, including enablement
and manual activation. Use this option with care. This honors the <option>--runtime</option> option to only
mask temporarily until the next reboot of the system. The <option>--now</option> option may be used to
ensure that the units are also stopped. This command expects valid unit names only, it does not accept unit
file paths.</para>
<para>Mask one or more units, as specified on the command line. This will link these unit files
to <filename>/dev/null</filename>, making it impossible to start them. This is a stronger version
of <command>disable</command>, since it prohibits all kinds of activation of the unit, including
enablement and manual activation. Use this option with care. This honors the
<option>--runtime</option> option to only mask temporarily until the next reboot of the
system. The <option>--now</option> option may be used to ensure that the units are also
stopped. This command expects valid unit names only, it does not accept unit file paths.</para>
<para>Note that this will create a symlink under the unit's name in
<filename>/etc/systemd/system/</filename> (in case <option>--runtime</option> is not specified)
or <filename>/run/systemd/system/</filename> (in case <option>--runtime</option> is
specified). If a matching unit file already exists under these directories this operation will
hence fail. This means that the operation is primarily useful to mask units shipped by the vendor
(as those are shipped in <filename>/usr/lib/systemd/system/</filename> and not the aforementioned
two directories), but typically doesn't work for units created locally (as those are typically
placed precisely in the two aforementioned directories). Similar restrictions apply for
<option>--user</option> mode, in which case the directories are below the user's home directory
however.</para>
</listitem>
</varlistentry>