7af88c1e1e
So far the idea was that the default is 'auto', and if appropriate, the distribution will create /var/log/journal/ to tell journald to use persistent mode. This doesn't work well with factory resets, because after a factory reset obviously /var/log is gone. That old default was useful when journald was new and people were reluctant to enable persistent mode and instead relied on rsyslog and such for the persistent storage. But nowadays that is rarer, and anyway various features like user journals only work with persistent storage, so we want people to enable this by default. Add an option to flip the default and distributions can opt in. The default default value remains unchanged. (I also tested using tmpfiles to instead change this, since we already set access mode for /var/log/journal through tmpfiles. Unfortunately, tmpfiles runs too late, after journald has already started, so if tmpfiles creates the directory, it'll only be used after a reboot. This probably could be made to work by adding a new service to flush the journal, but that becomes complicated and we lose the main advantage of simplicity.) Resolves https://bugzilla.redhat.com/show_bug.cgi?id=1387796.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS