From 8b7378e145522162b433ad59cf0a30fe66dfd6c3 Mon Sep 17 00:00:00 2001 From: Yu Watanabe Date: Wed, 30 Mar 2022 21:10:06 +0900 Subject: [PATCH] fix typo --- man/systemd.unit.xml | 2 +- src/shared/install.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index dd3553aa18d..7a611dc93f7 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -524,7 +524,7 @@ symlink target 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 /etc/systemd/system/alias1.service → service1.service, diff --git a/src/shared/install.c b/src/shared/install.c index f807947a3c6..8e81ec41bf7 100644 --- a/src/shared/install.c +++ b/src/shared/install.c @@ -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;