From 29920c5b1f73cc44399d2af23c428461dadb891e Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 19 Jan 2023 20:23:11 +0100 Subject: timesyncd: write structured log messages whenever we bump the clock based on disk timestamp MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It's useful being able to easily detect if a disk-based clock bump was done, let's make it a structure message, the same way as acquiring an NTP fix already is. Also, set the clock to 1 µs further than the timestamp from the disk, after all we know that that timestamp was current when it was written, hence it can't be the right one right now anymore. --- catalog/systemd.catalog.in | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'catalog') diff --git a/catalog/systemd.catalog.in b/catalog/systemd.catalog.in index 8d1812afcf..975e77fcec 100644 --- a/catalog/systemd.catalog.in +++ b/catalog/systemd.catalog.in @@ -528,6 +528,15 @@ Support: %SUPPORT_URL% For the first time during the current boot an NTP synchronization has been acquired and the local system clock adjustment has been initiated. +-- 7db73c8af0d94eeb822ae04323fe6ab6 +Subject: Initial clock bump +Defined-By: systemd +Support: %SUPPORT_URL% + +The system clock has been advanced based on a timestamp file on disk, in order +to ensure it remains roughly monotonic – even across reboots – if an RTC is not +available or is unreliable. + -- 3f7d5ef3e54f4302b4f0b143bb270cab Subject: TPM PCR Extended Defined-By: systemd -- cgit v1.2.1