tmpfiles: Order tmpfiles-setup after journald
systemd-tmpfiles-setup.service needs to be ordered after systemd-journald.service, so entries in /run/log/journal are already created when systemd-tmpfiles tries to adjust its permissions. This is specially problematic for setups using a volatile journal where the initrd does not ship a machine-id (i.e. OSTree-based systems), where logs from the initrd will be inaccessible for users in the systemd-journal group. It also has a side effect of `journalctl --user` failing with "No journal files were opened due to insufficient permissions". Fixes #10128.
This commit is contained in:
parent
3f491cccef
commit
5c86583cf8
|
@ -12,7 +12,7 @@ Description=Create Volatile Files and Directories
|
||||||
Documentation=man:tmpfiles.d(5) man:systemd-tmpfiles(8)
|
Documentation=man:tmpfiles.d(5) man:systemd-tmpfiles(8)
|
||||||
DefaultDependencies=no
|
DefaultDependencies=no
|
||||||
Conflicts=shutdown.target
|
Conflicts=shutdown.target
|
||||||
After=local-fs.target systemd-sysusers.service
|
After=local-fs.target systemd-sysusers.service systemd-journald.service
|
||||||
Before=sysinit.target shutdown.target
|
Before=sysinit.target shutdown.target
|
||||||
RefuseManualStop=yes
|
RefuseManualStop=yes
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue