Lennart Poettering
34af74946e
This is useful to later order boot IDs by time, addressing #662. Basically, this determines the most recently written for each boot ID from all currently open journal files. This is then stored in a hash table (which maps the boot ID to a prioq of journal files, ordered by their timestamp). Why is this useful? If systems lack a battery-buffered RTC they will initially have a system clock basically starting at zero. Later they might acquire an NTP fix, or at least roughly monotonic time via a stored timestamp. Thus, log entries written early during boot tend to be badly timestamped, and those written most recently are likely to have most accurate timestamps. Thus, if we track the newest entry for each boot ID we likely can order the boot ID via their timestamps. This commit only add the logic to maintain the hash table/prioq. It doesn't actually make use of this information for ordering yet. A later patch adds that.
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.