shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-01-20 14:03:39 +03:00
Code

docs: update unit name for sd-tmpfiles-setup

Browse Source 
(cherry picked from commit 7d33146dbc1bd727a2923bb2da54856a7cb15fb5)
This commit is contained in:
Mike Yuan 2023-03-19 01:32:50 +08:00 committed by Zbigniew Jędrzejewski-Szmek
parent f8b6d97185
commit 7b5b85286f
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README
View File

@ -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

2
docs/UIDS-GIDS.md
View File

@ -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.