diff options
author | Lennart Poettering <lennart@poettering.net> | 2023-02-08 13:40:10 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2023-03-02 10:18:24 +0100 |
commit | c48f13d8e17da57e225f692e1364cd554da3ac41 (patch) | |
tree | 441bc2da525a9d42d07a9b7a772e6d4593e7859b /TODO | |
parent | test: add test for journals without RTC (diff) | |
download | systemd-c48f13d8e17da57e225f692e1364cd554da3ac41.tar.xz systemd-c48f13d8e17da57e225f692e1364cd554da3ac41.zip |
update TODO
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -164,6 +164,16 @@ Features: * SIGRTMIN+18 and memory pressure handling should still be added to: hostnamed, localed, oomd, timedated. +* journald: also collect CLOCK_BOOTTIME timestamps per log entry. Then, derive + "corrected" CLOCK_REALTIME information on display from that and the timestamp + info of the newest entry of the specificy boot (as identified by the boot + ID). This way, if a system comes up without a valid clock but acquires a + better clock later, we can "fix" older entry timestamps on display, by + calculating backwards. We cannot use CLOCK_MONOTONIC for this, since it does + not account for suspend phases. This would then also enable us to correct the + kmsg timestamping we consume (where we erroneously assume the clock was in + CLOCK_MONOTONIC, but it actually is CLOCK_BOOTTIME as per kernel). + * sd-journal puts a limit on parallel journal files to view at once. journald should probably honour that same limit (JOURNAL_FILES_MAX) when vacuuming to ensure we never generate more files than we can actually view. |