User who is (only) in the group adm is able to view the volatile journal stored in /run/log.
Unexpected behaviour you saw
journalctl -b returns -- No entries --
Steps to reproduce the problem
Set Storage=volatile in journald.conf, reboot and run journalctl -b as non-root user who is in the adm group.
Additional program output to the terminal or log subsystem illustrating the issue
On boot the following error is logged:
systemd-tmpfiles[259]: Failed to parse ACL "d:group:adm:r-x,group:adm:r-X": Invalid argument. Ignoring
I'm assuming this is because 19904f50ac4ff786eba3fa958ab7c95e51b77d75 has been cherry-picked into 252 but support for X ACLs has only been added to 254: 26d98cdd78cb5283f5771bd5866997acc494b067
The same problem likely exists in 253-stable as well but I haven't tested that.
systemd version the issue has been seen with
252.25-1~deb12u1
Used distribution
Debian 12
Linux kernel version used
6.1.0-21-amd64
CPU architectures issue was seen on
x86_64
Component
systemd-tmpfiles
Expected behaviour you didn't see
User who is (only) in the group
admis able to view the volatile journal stored in /run/log.Unexpected behaviour you saw
journalctl -breturns-- No entries --Steps to reproduce the problem
Set
Storage=volatileinjournald.conf, reboot and runjournalctl -bas non-root user who is in theadmgroup.Additional program output to the terminal or log subsystem illustrating the issue
I'm assuming this is because 19904f50ac4ff786eba3fa958ab7c95e51b77d75 has been cherry-picked into 252 but support for
XACLs has only been added to 254: 26d98cdd78cb5283f5771bd5866997acc494b067The same problem likely exists in 253-stable as well but I haven't tested that.