[Git][NTPsec/ntpsec][master] Content of the STATUS file moves to the website.

Eric S. Raymond gitlab at mg.gitlab.com
Tue Sep 27 20:33:44 UTC 2016

Eric S. Raymond pushed to branch master at NTPsec / ntpsec

87acbfde by Eric S. Raymond at 2016-09-27T16:31:09-04:00
Content of the STATUS file moves to the website.

- - - - -

3 changed files:

- − devel/STATUS
- docs/clientstart.txt


@@ -45,7 +45,7 @@ libevent 2.x::
    NetBSD: As installed, libevent is broken.  It links, but doesn't run.
      Here is a workaround:
       # cd /usr/lib
-      # ln -s /usr/pkg/lib/libevent_core-2.0.so.5
+      # ln -s /usr/pkg/lib/libevent_core-2.0.so.5 .
    Optional on Linux to support restricting syscalls

devel/STATUS deleted
--- a/devel/STATUS
+++ /dev/null
@@ -1,33 +0,0 @@
-Last update, 2016 Jan 21
-It builds on the following systems.  In general there should be no warnings,
-but as of the above date, there is one we can't easily work around.  Some
-compilers will complain about
-  comparison between signed and unsigned integer expressions
-  at ntpd/ntp_io.c:4399
-We have reports that it builds cleanly on at least:
-  Fedora 23 and 24 (i686, x86_64)
-  CentOS 7.2.1511 and 6.8 (x86_64)
-  Debian jessie (amd64, i686, arm) and wheezy on amd64
-  Ubuntu 14.04.3 LTS and 16.04.1 LTS on x86_64
-  Raspbian jessie on ARM v6 and v7 (Pi, Pi 2, and Pi 3)
-  Debian wheezy on BeagleBone Black ARM v7
-  FreeBSD 10.2 and 9.3 on amd64 and 10.3 on i386
-  NetBSD 7.0.1 and 6.1.5 on x86_64 and 7.0.1 on i386
-    (see the comment about libevent in ../INSTALL)
-The basic parts of ntpd run on all of the above systems.
-There are many options that we haven't yet tested.
-Refclocks known to work on Linux:
-  20    NMEA GPS Receiver
-  22    PPS Clock Discipline
-  26    Hewlett Packard 58503A GPS Receiver
-  28    Shared Memory Driver
-  29    Trimble Navigation Palisade GPS (with Thunderbolt)
-  46    GPSD NG client protocol

--- a/docs/clientstart.txt
+++ b/docs/clientstart.txt
@@ -300,9 +300,10 @@ Next, you want to look at the line for "preferred" server (marked with
 NTP's algorithms have computed from its inputs. What you want to see here
 is low jitter. The PPS feed in the second example is pretty good. The
 figures from in the first display are not great, but
-they're not out of line for operation over a WAN.  Jitter over a
-second would indicate a serious problem, most likely due to
-asymmetric packet delays.
+they're not out of line for operation over a WAN.  Offset over a
+second is most likely due to asymmetric packet delays; large jitter
+is more likely due to bufferbloat and other sources of variable
+latency under load.

View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/87acbfde853280f5c5283c42ee4291b03a69e66f
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20160927/e9b15d97/attachment.html>

More information about the vc mailing list