aboutsummaryrefslogtreecommitdiffstats
path: root/doc/s6-sntpclock.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/s6-sntpclock.html')
-rw-r--r--doc/s6-sntpclock.html2
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>