[Git][NTPsec/ntpsec][master] Minor updates and typos for devel and docs

[Hal Murray]

Hal Murray pushed to branch master at NTPsec / ntpsec


Commits:
16aab7df by Hal Murray at 2016-09-26T12:30:26-07:00
Minor updates and typos for devel and docs

- - - - -


3 changed files:

- devel/STATUS
- devel/testing.txt
- docs/clientstart.txt


Changes:

=====================================
devel/STATUS
=====================================
--- a/devel/STATUS
+++ b/devel/STATUS
@@ -4,18 +4,18 @@ 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:4638
+  at ntpd/ntp_io.c:4399
 
 We have reports that it builds cleanly on at least:
-  Fedora 22 and 23 (i686, x86_64)
-  CentOS 5.11 (i386)
-  Debian wheezy (amd64)  and jessie (amd64, i686)
-  Ubuntu 14.04.3 LTS and 15.10 on x86_64
-  Raspbian wheezy and jessie on ARM v6 and v7 (Pi and Pi 2)
+  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 9.3 on i386 and 10.1 on amd64
-  NetBSD 6.1.5 and 7.0 on x86_64
+  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)
 
 


=====================================
devel/testing.txt
=====================================
--- a/devel/testing.txt
+++ b/devel/testing.txt
@@ -45,12 +45,12 @@ and restart ntpd.  The details vary by OS/distro.
 3. systemctl may barf about an out of date file and tell you
    how to fix it.  If so, follow its directions and try again.
 
-Note that underr Fedora and CentOS, "dnf update" may undo that edit
+Note that under Fedora and CentOS, "dnf update" may undo that edit
 and revert to running the system version.
 
 Older versions used /etc/rc.d/init.d/ntpd. The file /etc/sysconfig/ntpd
 gets sourced into the init script so you can put real code in there
-(systemd doesn't do that)/  You can insert this:
+(systemd doesn't do that)  You can insert this:
 
 --------------------------------------------------
     PATH="/usr/local/sbin:$PATH"
@@ -59,8 +59,8 @@ gets sourced into the init script so you can put real code in there
 === Debian, Ubuntu, Raspbian ===
 
 Many newer versions use systemd; follow those directions. The
-rest of this section the older set of conventions used with
-a traditional System V init sequence.
+rest of this section describes the older set of conventions used
+with a traditional System V init sequence.
 
 Edit /etc/init.d/ntp. Change
 


=====================================
docs/clientstart.txt
=====================================
--- a/docs/clientstart.txt
+++ b/docs/clientstart.txt
@@ -43,7 +43,7 @@ guide to reading it, but may not have to modify it at all.
 If you are using a typical residential setup, in which your machine
 performs DHCP to your ISP's servers and receives a dynamic address,
 your ntp.conf may be altered or generated by DHCP at
-address-allocation time.
+address-allocation time to use the NTP servers provided by DHCP.
 
 [[basics]]
 == Configuration basics ==
@@ -117,7 +117,7 @@ want to change them.
 == Configuring Pool Servers ==
 
 The NTP pool is a worldwide federation of public-facing NTP servers,
-almost always equipped with their own local reference clocks, that
+many equipped with their own local reference clocks, that
 have volunteered to provide time service to anyone who requests it
 through a pool dispatcher machine. The +server+ declarations in your
 /etc/ntp.conf normally point at several of these pool dispatchers.
@@ -222,9 +222,10 @@ HOWTO].
 == Special considerations when using DHCP ==
 
 If your machine uses DHCP to get a dynamic IP address from your ISP, 
-the ISP provides you with a list of NTP servers to use during that
-handshake.  Suspect this if, when you look at your ntp.conf, you
-see server domain names obviously belonging to your ISP.
+that handshake may provide you with a list of NTP servers.
+Suspect this if, when you look at your ntp.conf, you
+see server domain names obviously belonging to your ISP or
+your ntpq -p printout doesn't match what you expect.
 
 The way this works is that your DHCP client requests the list,
 then it restarts your +{ntpd}+ with a custom configuration file
@@ -255,9 +256,10 @@ that generate that file, or disable the generation process.
 [[sanity]]
 == Sanity-Checking Your Time Service ==
 
-Here's how to tell your time service is working.  Wait a few minutes
-for it to sync with upstream servers, then fire up ntpq with the -p
-(peers) option.  You should see a display looking something like this:
+Here's how to tell if and/or how well your time service is working.
+Wait a few minutes for it to sync with upstream servers, then fire
+up ntpq with the -p (peers) option.  You should see a display looking
+something like this:
 
 ------------------------------------------------------------------
      remote           refid      st t when poll reach   delay   offset  jitter



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/16aab7dfa7751b4a8afa960ab6878206a32e8d82
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20160926/170b2ae6/attachment.html>