[Git][NTPsec/ntpsec][master] More documentation polishing.
Eric S. Raymond
gitlab at mg.gitlab.com
Thu Sep 21 12:15:21 UTC 2017
Eric S. Raymond pushed to branch master at NTPsec / ntpsec
Commits:
5bba409c by Eric S. Raymond at 2017-09-21T12:14:39Z
More documentation polishing.
- - - - -
2 changed files:
- NEWS
- docs/ntpsec.txt
Changes:
=====================================
NEWS
=====================================
--- a/NEWS
+++ b/NEWS
@@ -3,19 +3,24 @@
For historic news from NTP Classic, see devel/HISTORIC-NEWS in the
distribution.
+Not all news features are described here; see docs/ntpsec.txt in the
+distribution.
+
Much of the traditional function of a news file is now better addressed
by browsing the comments in the revision history. This file will focus
on user-visible changes.
== Repository Head ==
-The code size has been further reduced, to 56KLOC.
+The code size has been further reduced, to 55KLOC.
+
+A bug inherited from Classic that could cause bad peer's jitter to be
+incorrectly zeroed, producing erratic or slow startup, has been fixed
-The depenendency local refclocks returning 4-digit years on
+The dependency of local refclocks returning 4-digit years on
pre-synchronization to a network peer has been removed. It is
this possible to run in a fully-autonomous mode using multiple
-refclocks and no network peers. (Note however that this mode
-is not yet well tested and may not be stable.)
+refclocks and no network peers.
ntpmon now reports units on time figures.
=====================================
docs/ntpsec.txt
=====================================
--- a/docs/ntpsec.txt
+++ b/docs/ntpsec.txt
@@ -162,7 +162,12 @@ codebase has been outright removed, with less than 5% new code added.
from the system clock. This means that (a) it is now possible for
ntpd using a local clock source to recover from a trashed or zeroed
system clock (e.g. at boot time on a system with missing or damaged
- vattery back up) without requiring sync to a remote peer.
+ battery back up) without requiring sync to a remote peer.
+
+* We've fixed bug inherited from Classic that could cause the jitter
+ of a bad peer to be incorrectly zeroed, possibly causing that peer
+ to be selected. This probably accounts for some flakiness within
+ 8 polling intervals of startup on older versions.
[[clients]]
== Client Tool Improvements ==
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/5bba409c52a4655e033de41910a3e0b5d894cd4b
---
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/5bba409c52a4655e033de41910a3e0b5d894cd4b
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20170921/8fa87dc2/attachment.html>
More information about the vc
mailing list