We always redirect PID1/journal coredumps directly onto disk instead of the journal even if that's configured because that might cause a deadlock because we are still pinning the old journal process while processing the coredump. However, so far we then immediately deleted the coredumps because of Storage=journal, which is very annoying, since there's hence no copy kept whatsoever. Let's hence exclude PID1+journal from the removal. This in particulary brings the code in line with the log messages which claim we kept the file around but we actually did not.
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
