From: Lennart Poettering Date: Fri, 11 Aug 2023 11:24:07 +0000 (+0200) Subject: man: don't claim BindPaths= file systems would remain "in memory", they are just... X-Git-Tag: v255-rc1~748 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=579fbe5b789cbee10546f6274c39be311e71e49c;p=thirdparty%2Fsystemd.git man: don't claim BindPaths= file systems would remain "in memory", they are just kept "mounted" Follow-up for: 947d836a6e86f1936250ff8e3c67fa33b92a597f (I guess in the original patch authors usecase the root fs actually *does* remain in memory, but that's a special case and does not belong in the man pages this way). --- diff --git a/man/systemd-soft-reboot.service.xml b/man/systemd-soft-reboot.service.xml index 711cd6e3e98..f7908d3f032 100644 --- a/man/systemd-soft-reboot.service.xml +++ b/man/systemd-soft-reboot.service.xml @@ -119,9 +119,9 @@ processes running during a soft-reboot operation requires disconnecting the service comprehensively from the rest of the OS, i.e. minimizing IPC and reducing sharing of resources with the rest of the OS. A possible mechanism to achieve this is the concept of Portable Services, but make sure no resource from - the host's root filesystem is pinned via BindPaths= or similar unit settings, - otherwise the old root filesystem will be kept in memory as long as the unit is running. + url="https://systemd.io/PORTABLE_SERVICES">Portable Services, but make sure no resource from the + host's OS filesystems is pinned via BindPaths= or similar unit settings, otherwise the + old, originating filesystem will remain mounted as long as the unit is running.