Hide Forgot
Description of problem: Removing /var/log/journal is documented and recommended as a way to configure journald will only use a volatile journal. However, because the systemd package owns directory /var/log/journal, the directory gets created and breaking this configuration every time systemd is updated. Version-Release number of selected component (if applicable): systemd-229-16.fc24.x86_64 How reproducible: Every time Steps to Reproduce: 1.rm -rf /var/log/journal &&systemctl restart systemd-journald 2.dnf upgrade systemd && systemctl restart systemd-journald 3.ls /var/log/journal Actual results: /var/log/journal is there again, and journald uses a non-volatile journal again Expected results: Still no /var/log/journal, and journal still in volatile storage Additional info:
http://pkgs.fedoraproject.org/cgit/rpms/systemd.git/commit/?id=4e1286dd8b6d12cc286dcc57e3ff69c00bd3c0e0
Thanks, Zbigniew! Looking at the patch, I'm missing code to play the role of %attrs for /var/log/journal where it is now created.
Look at the chunk starting with "# Make sure new journal files will be owned by the "systemd-journal" group". I think it should have the same effect.
systemd-231-10.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-005ad5dcb1
ah, yes, thanks, I concur, the chgrp and chmod commands will have the same effect. at least as long as %{_localstatedir} expands to /var ;-)
systemd-231-10.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.