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

fix typo

Browse Source
This commit is contained in:
Yu Watanabe 2022-03-30 21:10:06 +09:00
parent 8c70e8024b
commit 8b7378e145
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/systemd.unit.xml
View File

@ -524,7 +524,7 @@
symlink <emphasis>target</emphasis> is within the unit load path becomes an alias: the source name and
the target file name must satisfy specific constraints listed above in the discussion of aliases, but the
symlink target doesn't have to exist, and in fact the symlink target path is not used, except to check
whether the target is within the unit load path. In constrast, a symlink which goes outside of the unit
whether the target is within the unit load path. In contrast, a symlink which goes outside of the unit
load path signifies a linked unit file. The symlink is followed when loading the file, but the
destination name is otherwise unused (and may even not be a valid unit file name). For example, symlinks
<filename index='false'>/etc/systemd/system/alias1.service</filename> → <filename index='false'>service1.service</filename>,

2
src/shared/install.c
View File

@ -2797,7 +2797,7 @@ static int normalize_linked_files(
/* This is similar to normalize_filenames()/normalize_names() in src/systemctl/,
* but operates on real unit names. For each argument we we look up the actual path
* where the unit is found. This way linked units can be reenabled successfully. */
* where the unit is found. This way linked units can be re-enabled successfully. */
_cleanup_free_ char **files = NULL, **names = NULL;
int r;