Consider the following situation: - There are two journal files (x and y), that contains entries for two boots (X and Y). - The journal file x contains entries of the boot X, and y contains entries of Y. - Nevertheless x does not contains entries of boot Y, it contains the _BOOT_ID= data object of boot Y. Of course, the data object is not referenced by any entries in the journal file x. In such situation, when the current location of sd_journal is the head of journal y, that is, the first entry of the boot Y, sd_journal_previous() failed without this change, and 'journalctl --boot -NUM' for boot X failed. Fixes #29275.
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
