From b63c88b6271804e4770a14d94c66210e0c8063d7 Mon Sep 17 00:00:00 2001 From: HATAYAMA Daisuke Date: Tue, 17 Dec 2019 22:01:42 -0500 Subject: [PATCH] man: describe "symlink" and "systemctl link" explicitly in UNIT FILE LOAD PATH There are sometimes users who put unit files in a location that is inaccessible when systemd starts although they are not found and thus not started because the corresponding mount units have not activated yet. There is already a warning for such issue in man 8 systemctl: link PATH... ...... The file system where the linked unit files are located must be accessible when systemd is started (e.g. anything underneath /home or /var is not allowed, unless those directories are located on the root file system). However, it looks that it's difficult to find the warning because introductory users typically doesn't know systemctl link. Although there is a description in UNIT FILE LOAD PATH pointing to systemctl link, symlink is now not explicitly mentioned there and thus users doesn't easily get aware of they should read it. To deal with this, let's describe "symlink" and "systemctl link" more explicitly in UNIT FILE LOAD PATH. --- man/systemd.unit.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 93c4a28d22..8e2765c860 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -467,10 +467,12 @@ systemd-analyze --user unit-paths - Moreover, additional units might be loaded into systemd ("linked") from - directories not on the unit load path. See the link command - for - systemctl1. + Moreover, additional units might be loaded into systemd from + directories not on the unit load path by creating a symlink pointing to a + unit file in the directories. You can use systemctl link + for this operation. See + systemctl1 + for its usage and precaution.