From cd3522eb8565588582ac41eddf6f7f078b069439 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 4 Oct 2020 17:41:09 +0000 Subject: doc: fix URLs --- doc/s6-sntpclock.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/s6-sntpclock.html') diff --git a/doc/s6-sntpclock.html b/doc/s6-sntpclock.html index 823557c..156dacc 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. @@ -106,9 +106,9 @@ do so.

From a Unix software engineering standpoint, the well-known -ntpd program is an +ntpd program is an eldritch abomination. The main reason for it is that, just like its -lovely cousin BIND, +lovely cousin BIND, ntpd performs a lot of different tasks in a unique process, instead of separating what could, and should, be separated. This is confusing for both the programmer and the software user. @@ -133,7 +133,7 @@ is the regular setting of the system clock, which can be done with a loop over a simple program such as s6-clockadd. There is also control of the clock skew, which s6-networking does not provide because there is no portable interface for that; there is such a tool -in the clockspeed package. +in the clockspeed package.

  • ntpd includes a complete cryptographic key management system for the crypto part of NTP. NTP is not the only protocol that uses cryptography and asymmetric keys; managing keys in a separate tool, not in the NTP -- cgit v1.3.1