From: adrian5 Date: Mon, 29 Aug 2022 02:24:56 +0000 (+0200) Subject: man: Minor punctuation and word tweak X-Git-Tag: v252-rc1~306 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b72e5d9d8ef17d87b4e94c370e90545e47053329;p=thirdparty%2Fsystemd.git man: Minor punctuation and word tweak --- diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 2e843be2e54..0a2b6da7725 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -1273,7 +1273,7 @@ CapabilityBoundingSet=~CAP_B CAP_C directories to be made visible when listed in BindPaths= or BindReadOnlyPaths=. - Setting this to yes is mostly equivalent to set the three directories in + Setting this to yes is mostly equivalent to setting the three directories in InaccessiblePaths=. Similarly, read-only is mostly equivalent to ReadOnlyPaths=, and tmpfs is mostly equivalent to TemporaryFileSystem= with :ro. @@ -1515,7 +1515,7 @@ StateDirectory=aaa/bbb ccc Note that these settings will disconnect propagation of mounts from the unit's processes to the host. This means that this setting may not be used for services which shall be able to install mount points in - the main mount namespace. For ReadWritePaths= and ReadOnlyPaths= + the main mount namespace. For ReadWritePaths= and ReadOnlyPaths=, propagation in the other direction is not affected, i.e. mounts created on the host generally appear in the unit processes' namespace, and mounts removed on the host also disappear there too. In particular, note that mount propagation from host to unit will result in unmodified mounts to be created in the unit's namespace,