diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2025-04-28 08:44:10 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska@appnovation.com> | 2025-04-28 08:44:10 +0000 |
| commit | e903d827b91202cb890b638419cc9409cde1b9d5 (patch) | |
| tree | 67fd564073609177b386861eb7596cbbeee1f90e /doc/s6-sntpclock.html | |
| parent | 9499f0c51f3163dd6f7a5f7812b00897b049d139 (diff) | |
| download | s6-networking-e903d827b91202cb890b638419cc9409cde1b9d5.tar.gz | |
Latest batch of fixes
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc/s6-sntpclock.html')
| -rw-r--r-- | doc/s6-sntpclock.html | 2 |
1 files changed, 1 insertions, 1 deletions
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 -<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html">date</a> or +<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/date.html">date</a> or <a href="//skarnet.org/software/s6-portable-utils/s6-clock.html">s6-clock</a> to a closer time (such as 2013-01-01, which will be good up to 2047), then contact the NTP server. </li> |