docs: update unit name for sd-tmpfiles-setup

diff --git a/README b/README
index a94f71cc6670a3923ebb3d0fa7a2560527eaffcc..e60ff16ef1128651329bb9e6d2397382d135e9e0 100644 (file)
--- a/README
+++ b/README
@@ -305,7 +305,7 @@ USERS AND GROUPS:
         group to exist. New journal files will be readable by this group (but
         not writable), which may be used to grant specific users read access. In
         addition, system groups "wheel" and "adm" will be given read-only access
-        to journal files using systemd-tmpfiles.service.
+        to journal files using systemd-tmpfiles-setup.service.
 
         The journal remote daemon requires the "systemd-journal-remote" system
         user and group to exist. During execution this network facing service

diff --git a/docs/UIDS-GIDS.md b/docs/UIDS-GIDS.md
index 57e8f4d4f5b36713e7444182f55d3930d00067c9..db4cac4cc328559d759c3e88b565b149498a882c 100644 (file)
--- a/docs/UIDS-GIDS.md
+++ b/docs/UIDS-GIDS.md
@@ -301,7 +301,7 @@ means they should not be provided by any networked service (as those usually
 become available during late boot only), except if a local cache is kept that
 makes them available during early boot too (i.e. before networking is
 up). Specifically, system users need to be resolvable at least before
-`systemd-udevd.service` and `systemd-tmpfiles.service` are started, as both
+`systemd-udevd.service` and `systemd-tmpfiles-setup.service` are started, as both
 need to resolve system users — but note that there might be more services
 requiring full resolvability of system users than just these two.