summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2023-02-08 13:40:10 +0100
committerLennart Poettering <lennart@poettering.net>2023-03-02 10:18:24 +0100
commitc48f13d8e17da57e225f692e1364cd554da3ac41 (patch)
tree441bc2da525a9d42d07a9b7a772e6d4593e7859b /TODO
parent4601c7aa8ff626f52de3f69b27602c6978bd84db (diff)
downloadsystemd-c48f13d8e17da57e225f692e1364cd554da3ac41.tar.gz
update TODO
Diffstat (limited to 'TODO')
-rw-r--r--TODO10
1 files changed, 10 insertions, 0 deletions
diff --git a/TODO b/TODO
index 263c4b4e6b..bf4c55cb5b 100644
--- a/TODO
+++ b/TODO
@@ -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.