From e903d827b91202cb890b638419cc9409cde1b9d5 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Apr 2025 08:44:10 +0000 Subject: Latest batch of fixes Signed-off-by: Laurent Bercot --- doc/s6-sntpclock.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/s6-sntpclock.html') diff --git a/doc/s6-sntpclock.html b/doc/s6-sntpclock.html index 3403226..40e98a2 100644 --- a/doc/s6-sntpclock.html +++ b/doc/s6-sntpclock.html @@ -86,7 +86,7 @@ server is more than 34 years away from the time given by the system clock, then NTP just cannot compute. This is a problem for CMOS-less systems, where the system clock is initialized to the Unix Epoch. The solution is to first manually initialize the system clock with a program such as -date or +date or s6-clock to a closer time (such as 2013-01-01, which will be good up to 2047), then contact the NTP server. -- cgit v1.3.1