[Git][NTPsec/ntpsec][master] 9 commits: Remove stray markup and clean up parameter names
Eric S. Raymond
gitlab at mg.gitlab.com
Sun Dec 25 10:23:07 UTC 2016
Eric S. Raymond pushed to branch master at NTPsec / ntpsec
Commits:
7060405a by Matt Selsky at 2016-12-25T05:21:41-05:00
Remove stray markup and clean up parameter names
Make sure the Synopsis and Description agree on the parameter names
- - - - -
992d72af by Matt Selsky at 2016-12-25T05:21:41-05:00
Typos, markup fixes
- - - - -
50579f96 by Matt Selsky at 2016-12-25T05:21:41-05:00
IPv6 doesn't use classful addressing
- - - - -
ce16a116 by Matt Selsky at 2016-12-25T05:21:41-05:00
Spelling
- - - - -
c5698695 by Sanjeev Gupta at 2016-12-25T05:22:50-05:00
Fix couple of typos
- - - - -
02ea3b19 by Sanjeev Gupta at 2016-12-25T05:22:50-05:00
Whitespace changes to align fields
amd some minor copy-editing
- - - - -
e1413d58 by Sanjeev Gupta at 2016-12-25T05:22:50-05:00
Minor whitespace and formatting
- - - - -
8af669fc by Sanjeev Gupta at 2016-12-25T05:22:50-05:00
Fix whitespace and alignment
- - - - -
3981d852 by Sanjeev Gupta at 2016-12-25T05:22:50-05:00
Finish up whitespace fixes ...
... for now
- - - - -
28 changed files:
- NEWS
- docs/asciidoc.css
- docs/decode.txt
- docs/driver_generic.txt
- docs/driver_gpsd.txt
- docs/driver_jjy.txt
- docs/driver_magnavox.txt
- docs/driver_modem.txt
- docs/driver_neoclock.txt
- docs/driver_trimble.txt
- docs/generic_howto.txt
- docs/huffpuff.txt
- docs/includes/ntpq-body.txt
- docs/includes/ntpsweep-body.txt
- docs/includes/ntpwait-body.txt
- docs/leap.txt
- docs/mode6.txt
- docs/mx4200data.txt
- docs/ntp_conf.txt
- docs/ntpkeygen.txt
- docs/ntpsec.txt
- docs/ntpspeak.txt
- docs/oncore-shmem.txt
- docs/parsedata.txt
- docs/quick.txt
- docs/rdebug.txt
- docs/tf582_4.txt
- ntpd/ntp.conf-man.txt
Changes:
=====================================
NEWS
=====================================
--- a/NEWS
+++ b/NEWS
@@ -119,7 +119,7 @@ or web chatter around it for a decade.
The audio-path drivers (IRIG and CHU) have been removed. The class
of hardware required to support them has gone essentially extinct due
-to cheap DSP. The complexity/maintainance overhead of this code
+to cheap DSP. The complexity/maintenance overhead of this code
was high enough to motivate dropping them.
This release contains a fix for one vulnerability inherited from
@@ -164,7 +164,7 @@ vulnerability: ephemeral association attack (Credit: Matthew van Gundy
of Cisco ASIG) as a duplicate of CVE-2015-7974 (see 0.9.1 release
notes) and it is WONTFIX for the time being: it is
correct-but-unfortunate behavior consequent to confusing and
-inflexible semantics of ntp.conf's acess control language, and we
+inflexible semantics of ntp.conf's access control language, and we
will address it with a future redesign effort. NTP Classic has
partially addressed this pair of issues by extending the syntax of
ntp.keys to support IP ACLing. We are not currently aware of any
=====================================
docs/asciidoc.css
=====================================
--- a/docs/asciidoc.css
+++ b/docs/asciidoc.css
@@ -484,7 +484,7 @@ thead, p.table.header {
p.table {
margin-top: 0;
}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
+/* Because the table frame attribute is overridden by CSS in most browsers. */
div.tableblock > table[frame="void"] {
border-style: none;
}
=====================================
docs/decode.txt
=====================================
--- a/docs/decode.txt
+++ b/docs/decode.txt
@@ -246,7 +246,7 @@ It consists of a number of bits coded in hexadecimal as follows:
|==============================================================================
The "Tag" field is the name the source code uses for the status bit.
-Not all bits are in use, but have been kept for backwards compatibility.
+Not all bits are in use, but have been kept for backwards compatibility.
[[kiss]]
== Kiss Codes ==
=====================================
docs/driver_generic.txt
=====================================
--- a/docs/driver_generic.txt
+++ b/docs/driver_generic.txt
@@ -124,7 +124,7 @@ SEL-2407 in one of its development labs.
*http://www.meinberg.de[Meinberg] https://www.meinbergglobal.com/english/archive/pzf511.htm[PZF5xx receiver family] (FM demodulation/TCXO / 50μs)*
+
WARNING: This equipment is no longer available for commercial sale, and
-support may be removed in the future. See:
+support may be removed in the future. See:
https://www.ntpsec.org/removal-plan.html[Feature removals]
* *refclock generic subtype 1*
@@ -132,7 +132,7 @@ https://www.ntpsec.org/removal-plan.html[Feature removals]
*http://www.meinberg.de[Meinberg] https://www.meinbergglobal.com/english/archive/pzf511.htm[PZF5xx receiver family] (FM demodulation/OCXO / 50μs)*
+
WARNING: This equipment is no longer available for commercial sale, and
-support may be removed in the future. See:
+support may be removed in the future. See:
https://www.ntpsec.org/removal-plan.html[Feature removals]
image::pic/pzf511.jpg[http://www.meinberg.de/english/products/pzf-eurocard.htm]
@@ -161,7 +161,7 @@ that comes with the Meinberg driver package.
http://www.elv.de/[ELV] *DCF7000 (sloppy AM demodulation / 50ms)*
+
WARNING: This equipment is no longer available for commercial sale, and
-support may be removed in the future. See:
+support may be removed in the future. See:
https://www.ntpsec.org/removal-plan.html[Feature removals]
* *refclock generic subtype 4*
@@ -169,7 +169,7 @@ https://www.ntpsec.org/removal-plan.html[Feature removals]
*Walter Schmid DCF receiver Kit (AM demodulation / 1ms)*
+
WARNING: This equipment is no longer available for commercial sale, and
-support may be removed in the future. See:
+support may be removed in the future. See:
https://www.ntpsec.org/removal-plan.html[Feature removals]
* *refclock generic subtype 5*
@@ -210,7 +210,7 @@ image:pic/igclock.gif[http://www.igel.de/eigelmn.html]
*http://www.trimble.com[Trimble] ftp://ftp.trimble.com/pub/sct/embedded/bin/Data%20Sheets/SveeSix2.PDF[SVeeSix GPS receiver] TAIP protocol (GPS / <<1μs)*
+
WARNING: This equipment is no longer available for commercial sale, and
-support may be removed in the future. See:
+support may be removed in the future. See:
https://www.ntpsec.org/removal-plan.html[Feature removals]
* *refclock generic subtype 10*
@@ -218,7 +218,7 @@ https://www.ntpsec.org/removal-plan.html[Feature removals]
*http://www.trimble.com[Trimble] ftp://ftp.trimble.com/pub/sct/embedded/bin/Data%20Sheets/SveeSix2.PDF[SVeeSix GPS receiver] (GPS / <<1μs) (no kernel support yet)*
+
WARNING: This equipment is no longer available for commercial sale, and
-support may be removed in the future. See:
+support may be removed in the future. See:
https://www.ntpsec.org/removal-plan.html[Feature removals]
+
image:pic/pd_om011.gif[http://www.trimble.com/cgi/omprod.cgi/pd_om011.html]
@@ -365,7 +365,7 @@ First let ntpq display the table of associations:
===========================================================
1 19556 9154 yes yes none falsetick reachable 5
2 19557 9435 yes yes none candidat clock expt 3
- 3 19558 9714 yes yes none pps.peer reachable 1
+ 3 19558 9714 yes yes none pps.peer reachable 1
-------------------------------------------------------------
@@ -375,14 +375,14 @@ several queries.
----------------------------------------
ntpq> raw
- Output set to raw
+ Output set to raw
----------------------------------------
Use the cv command to read the list of clock variables of a selected
association:
----------------------------------------
- ntpq> cv 19557 clock_var_list
+ ntpq> cv 19557 clock_var_list
----------------------------------------
The long output of the command above looks similar to:
@@ -394,14 +394,14 @@ The long output of the command above looks similar to:
refclock_format,refclock_states,refclock_id,refclock_iomode,refclock_driver_version,
meinberg_gps_status,gps_utc_correction,gps_message,meinberg_antenna_status,gps_tot_51,
gps_tot_63,gps_t0a,gps_cfg[1],gps_health[1],gps_cfg[2],gps_health[2],gps_cfg[3],
- gps_health[3],gps_cfg[4],gps_health[4],gps_cfg[5]"
+ gps_health[3],gps_cfg[4],gps_health[4],gps_cfg[5]"
----------------------------------------
Then use the cv command again to list selected clock variables. The
following command must be entered as a single line:
----------------------------------------
- ntpq> cv 19557 refclock_status,refclock_format,refclock_states,refclock_id, refclock_iomode,refclock_driver_version,meinberg_gps_status,gps_utc_correction, gps_message,meinberg_antenna_status,gps_tot_51,gps_tot_63,gps_t0a,gps_cfg[1], gps_health[1],gps_cfg[2],gps_health[2],gps_cfg[3],gps_health[3],gps_cfg[4], gps_health[4],gps_cfg[5]
+ ntpq> cv 19557 refclock_status,refclock_format,refclock_states,refclock_id, refclock_iomode,refclock_driver_version,meinberg_gps_status,gps_utc_correction, gps_message,meinberg_antenna_status,gps_tot_51,gps_tot_63,gps_t0a,gps_cfg[1], gps_health[1],gps_cfg[2],gps_health[2],gps_cfg[3],gps_health[3],gps_cfg[4], gps_health[4],gps_cfg[5]
----------------------------------------
The output of the command above is wrapped around depending on the
@@ -428,7 +428,7 @@ screen width and looks similar to:
gps_cfg[2]="[0x0] BLOCK I", gps_health[2]="[0x3f] PARITY;MULTIPLE ERRS",
gps_cfg[3]="[0x9] BLOCK II", gps_health[3]="[0x0] OK;SIGNAL OK",
gps_cfg[4]="[0x9] BLOCK II", gps_health[6]="[0x0] OK;SIGNAL OK",
- gps_cfg[5]="[0x9] BLOCK II"
+ gps_cfg[5]="[0x9] BLOCK II"
----------------------------------------
== Driver Options ==
=====================================
docs/driver_gpsd.txt
=====================================
--- a/docs/driver_gpsd.txt
+++ b/docs/driver_gpsd.txt
@@ -6,7 +6,7 @@
["verse",subs="normal"]
Name: gpsd
Reference ID: GPSD
-Serial Port: /dev/gps__u__
+Serial Port: /dev/gps__u__
== Description ==
=====================================
docs/driver_jjy.txt
=====================================
--- a/docs/driver_jjy.txt
+++ b/docs/driver_jjy.txt
@@ -31,10 +31,10 @@ refclock jjy unit X subtype 1 time1 0.NNN flag1 {0|1};;
time from the receiver, a fixed-point decimal number in seconds. You
may specify the time offset from several tens of milliseconds (
0.0NN seconds ) to a hundred and several tens of milliseconds (
- 0.1NN seconds ) for this clock. +
+ 0.1NN seconds ) for this clock. +
Flag1 has no effect for time synchronization. When flag1 is set to
1, status commands are issued before DATE and STIM commands, and
- write a response text into the clockstats file.
+ write a response text into the clockstats file.
+
[width="100%",cols="<50%,<50%",]
|====================================
=====================================
docs/driver_magnavox.txt
=====================================
--- a/docs/driver_magnavox.txt
+++ b/docs/driver_magnavox.txt
@@ -90,7 +90,7 @@ refclock magnavox
== Additional Information ==
-link:refclock.html[Reference Clock Drivers]
+link:refclock.html[Reference Clock Drivers]
'''''
=====================================
docs/driver_modem.txt
=====================================
--- a/docs/driver_modem.txt
+++ b/docs/driver_modem.txt
@@ -172,7 +172,7 @@ David L. Mills <mills at udel.edu>
== Additional Information ==
-link:refclock.html[Reference Clock Drivers]
+link:refclock.html[Reference Clock Drivers]
'''''
=====================================
docs/driver_neoclock.txt
=====================================
--- a/docs/driver_neoclock.txt
+++ b/docs/driver_neoclock.txt
@@ -15,7 +15,7 @@ The refclock_neoclock4x driver supports the NeoClock4X receiver
available from http://www.linum.com[Linum Software GmbH]. The receiver
is available as a http://www.dcf77.de[DCF77] or TDF receiver. Both
receivers have the same output string. For more information about the
-NeoClock4X receiver please visit http://www.linux-funkuhr.de.
+NeoClock4X receiver please visit http://www.linux-funkuhr.de.
== Driver Options ==
=====================================
docs/driver_trimble.txt
=====================================
--- a/docs/driver_trimble.txt
+++ b/docs/driver_trimble.txt
@@ -64,7 +64,8 @@ Palisade's external event input with 40 nanosecond resolution is
utilized by the Trimble NTP driver for asynchronous precision time
transfer.
-No user initialization of the receiver is required. This driver is compatible with the following versions of Palisade:
+No user initialization of the receiver is required. This driver is
+compatible with the following versions of Palisade:
[width="50%",cols="<34%,<33%,<33%",align="center",frame="none",grid="none"]
|======================================================
@@ -74,8 +75,10 @@ No user initialization of the receiver is required. This driver is compatible wi
| 7.12 | Yes | 38158-00
|======================================================
-Note: When using Palisade 26664-00, you must set the +flag2+ option to 1 in
-*{ntpconf}*. See link:#Configuration[configuration].
+When using Palisade 26664-00, you must set the +flag2+ option to
+1 in {ntpconf}.
+
+See Configuration[configuration].
== GPS Installation ==
@@ -331,17 +334,17 @@ Bit 7: (1) Leap In Progress. Only set during the leap second.
.*Packet 8F-0B (Comprehensive Timing Packet)*
[width="50%",cols="<25%,<25%,<25%,<25%",frame="none",grid="none",style="verse"]
|=========================================
-| Byte | Item | Type | Meaning
+| Byte | Item | Type | Meaning
| 0 | Sub-Packet ID | BYTE | Subcode 0x0B
| 1 - 2 | Event Count | INTEGER | External event count recorded (0 = PPS)
| 3 - 10 | UTC / GPS TOW | DOUBLE | UTC / GPS time of week (seconds)
| 11 | Date | BYTE | Day of Month
| 12 | Month | BYTE | Month of Event
| 13 - 14 | Year | INT | Year of event
-| 15 | Receiver Mode | BYTE | Receiver operating dimensions:
- 0: Horizontal (2D)
- 1: Full Position (3D)
- 2: Single Satellite (0D)
+| 15 | Receiver Mode | BYTE | Receiver operating dimensions:
+ 0: Horizontal (2D)
+ 1: Full Position (3D)
+ 2: Single Satellite (0D)
3: Automatic (2D / 3D)
4: DGPS reference
5: Clock hold (2D)
@@ -386,12 +389,12 @@ Thunderbolt can output 2 synchronous packets.
[width="50%",frame="none",grid="none",style="verse",options="header"]
|=================================================================================
|Byte | Bit | Item | Type | Value | Description
-| 0 | | Subcode | UINT8 | | 0xAC
-| 1 | | Receiver Mode | UINT8 | 0 | Automatic (2D/3D)
+| 0 | | Subcode | UINT8 | | 0xAC
+| 1 | | Receiver Mode | UINT8 | 0 | Automatic (2D/3D)
| | | | | 1 | Single Satellite (Time)
| | | | | 2 | Horizontal (2D)
-| | | | | 3 | Full Position (3D)
-| | | | | 4 | DGPS Reference
+| | | | | 3 | Full Position (3D)
+| | | | | 4 | DGPS Reference
| | | | | 5 | Clock Hold (2D)
| | | | | 6 | Overdetermined Clock
| 2 | | Disciplining Mode | UINT8 | 0 | Normal
=====================================
docs/generic_howto.txt
=====================================
--- a/docs/generic_howto.txt
+++ b/docs/generic_howto.txt
@@ -65,7 +65,6 @@ These are feature flags denoting items that are supported by the clock:
PARSEB_S_ANTENNA supports ANTENNA - might set PARSEB_ALTERNATE
PARSEB_S_PPS supports PPS time stamping
PARSEB_S_POSITION supports position information (GPS)
-
----------------------------------------------------------------------------
+
If the utctime field is non-zero this value will be take as time code
@@ -109,7 +108,7 @@ struct clockformat
u_long (*convert)();
/* conversion routine - your routine - cvt_<yourclock> */
/* routine for handling RS232 sync events (time stamps) - usually sync_simple */
- u_long (*syncpps)();
+ u_long (*syncpps)();
/* PPS input routine - usually pps_one */
void *data;
/* local parameters - any parameters/data/configuration info your conversion
@@ -187,7 +186,7 @@ clocks for example)
u_char cl_type; /* clock type (ntp control) */
Type if clock as in clock status word (ntp control messages) - usually 0
-
+
u_long cl_maxunsync; /* time to trust oscillator after losing synch
*/
seconds a clock can be trusted after losing synchronisation.
=====================================
docs/huffpuff.txt
=====================================
--- a/docs/huffpuff.txt
+++ b/docs/huffpuff.txt
@@ -34,11 +34,11 @@ that the samples are clustered close to the upper limb line,
representing heavy traffic in the download direction. The apparent
offset 'y'~0~ is near zero at the minimum delay 'x'~0~, which is near
0.1s. +
-
+
Thus, for a point ('x', 'y'), the true offset is::
θ = 'y' - ('x' - 'x'~0~) / 2 for 'y' > 'y'~0~ at or near the upper limb line or
-+
++
θ = 'y' + ('x' - 'x'~0~) / 2 for 'y' < 'y'~0~ at or near the lower limb line.
In either case the associated delay is δ = 'x'.
=====================================
docs/includes/ntpq-body.txt
=====================================
--- a/docs/includes/ntpq-body.txt
+++ b/docs/includes/ntpq-body.txt
@@ -274,7 +274,7 @@ ind assid status conf reach auth condition last_event cnt
+monstats+::
Display monitor facility statistics.
-+direct::
++direct+::
Normally, the mrulist command retrieves an entire MRUreport (possibly
consisting of more than one MRU span), sorts it, and presents the
result. But attempting to fetch an entire MRU report may fail on a
=====================================
docs/includes/ntpsweep-body.txt
=====================================
--- a/docs/includes/ntpsweep-body.txt
+++ b/docs/includes/ntpsweep-body.txt
@@ -1,4 +1,4 @@
-// This is the body of the manual page for ntmon.
+// This is the body of the manual page for ntpsweep.
// It's included in two places: once for the docs/ HTML
// tree, and once to make an individual man page.
=====================================
docs/includes/ntpwait-body.txt
=====================================
--- a/docs/includes/ntpwait-body.txt
+++ b/docs/includes/ntpwait-body.txt
@@ -8,9 +8,9 @@ The +ntpwait+ program blocks until ntpd is in synchronized state. This
can be useful at boot time, to delay the boot sequence until after "ntpd
-g" has set the time.
-+ntpwait+ will send at most _num-tries_ queries to {ntpdman}, sleeping
-for _secs-between_ after each status return that says {ntpdman} has not
-yet produced a synchronized and stable system clock._
++ntpwait+ will send at most _number_ queries to {ntpdman}, sleeping
+for _secs_ seconds after each status return that says {ntpdman} has not
+yet produced a synchronized and stable system clock.
+ntpwait+ will do this quietly, unless the +-v+ flag is provided.
=====================================
docs/leap.txt
=====================================
--- a/docs/leap.txt
+++ b/docs/leap.txt
@@ -3,7 +3,7 @@
Every six months the International Earth Rotation Service
(IERS) issues a bulletin announcing if there will be a leap second in
the Universal Coordinated Time (UTC) timescale. Historically,
-only insertions have occurred, about every eighteen months. The changes
+only insertions have occurred, about every eighteen months. The changes
have been at the end of the last day of June or December; but, in principle,
it could happen at the end of any month. While these bulletins are
available on the Internet at https://www.iers.org[www.iers.org], advance
=====================================
docs/mode6.txt
=====================================
--- a/docs/mode6.txt
+++ b/docs/mode6.txt
@@ -385,7 +385,7 @@ client that is willing to accumulate an entire set of MRU list
fragments and then perform stale-record elimination of its own before
displaying or passing on the report (that is, as opposed to
incremental display with an attempt to suppress stale records on the
-fly).
+fly).
=== CTL_OP_READ_ORDLIST_A ===
=====================================
docs/mx4200data.txt
=====================================
--- a/docs/mx4200data.txt
+++ b/docs/mx4200data.txt
@@ -6,10 +6,10 @@
** link:#input_000[$PMVXG,000] Initialization/Mode Control - Part A
** link:#input_001[$PMVXG,001] Initialization/Mode Control - Part B
** link:#input_007[$PMVXG,007] Control Port Configuration
-** link:#input_023[$PMVXG,023] Time Recovery Configuration
-** link:#input_gpq[$CDGPQ,YYY] Query From a Remote Device / Request to Output a Sentence
+** link:#input_023[$PMVXG,023] Time Recovery Configuration
+** link:#input_gpq[$CDGPQ,YYY] Query From a Remote Device / Request to Output a Sentence
* link:#output[Control Port Output Sentences]
-** link:#output_000[$PMVXG,000] Receiver Status
+** link:#output_000[$PMVXG,000] Receiver Status
** link:#output_021[$PMVXG,021] Position, Height, Velocity
** link:#output_022[$PMVXG,022] DOPs
** link:#output_030[$PMVXG,030] Software Configuration
@@ -24,7 +24,7 @@ The Control (CDU) Port is used to initialize, monitor, and control the
receiver. The structure of the control port sentences is based on the
_NMEA-0183_ Standard for Interfacing Marine Electronics Navigation Devices
(version 1.5). For more details, please refer to the _NMEA-0183_
-Specification available from the http://www.nmea.org/[National Marine
+Specification available from the https://www.nmea.org/[National Marine
Electronics Association].
Reserved characters are used to indicate the beginning and the end of
@@ -147,7 +147,7 @@ DOP limits, and satellite elevation limits.
[width="99%",cols="<10%,<26%,<16%,<16%,<16%,<16%",options="header"]
|=============================================================================
| Field | Description | Units | Format | Default | Range
-| *1 | Constrain Altitude | | Int | 1 | 0=3D Only
+| *1 | Constrain Altitude | | Int | 1 | 0=3D Only
1=Auto
2=2D Only
| 2 | Not Used | | | |
=====================================
docs/ntp_conf.txt
=====================================
--- a/docs/ntp_conf.txt
+++ b/docs/ntp_conf.txt
@@ -186,7 +186,7 @@ with the non-terminals. The types of the non-terminals are specified
with a +%type+ declaration as shown below:
-----------------------
-%type <Queue> address_list
+%type <Queue> address_list
%type <Integer> boolean
-----------------------
=====================================
docs/ntpkeygen.txt
=====================================
--- a/docs/ntpkeygen.txt
+++ b/docs/ntpkeygen.txt
@@ -30,7 +30,7 @@ include::includes/manual.txt[]
include::includes/ntpkeygen-body.txt[]
-// The end of "Cryptographic Data Files" runs into this following text.
+// The end of "Cryptographic Data Files" runs into this following text.
image:pic/sx5.gif[]
=====================================
docs/ntpsec.txt
=====================================
--- a/docs/ntpsec.txt
+++ b/docs/ntpsec.txt
@@ -22,7 +22,7 @@ Accept no imitations.
* link:#configuration[Configuration Improvements]
* link:#other[Other user-visible changes]
-[[intro]]
+[[intro]]
== Introduction ==
The design objectives of this distribution, NTPsec, are in
@@ -209,7 +209,7 @@ codebase has been outright removed, with less than 5% new code added.
directory name of the last pushed file in the stack. This means
that you can run ntpd from any directory with "includefile foo"
in /etc/ntp.conf finding /etc/foo rather than looking for foo in
- ypur current directory.
+ your current directory.
* It is now possible to set the peer maximum dispersion with "tos
maxdisp". See RFC 5905 for discussion of this synchronization
=====================================
docs/ntpspeak.txt
=====================================
--- a/docs/ntpspeak.txt
+++ b/docs/ntpspeak.txt
@@ -247,7 +247,7 @@
http://www.usno.navy.mil/USNO[The United States Naval Observatory],
one of the two U.S. national time authorities and the source of the
U.S. military time reference, now delivered primarily by GPS
- signals. U.S. civil <<NIST>> and military <<USNO>> time agree to
+ signals. U.S. civil <<NIST>> and military <<USNO>> time agree to
within nanoseconds.
[[WWVB]] WWVB::
=====================================
docs/oncore-shmem.txt
=====================================
--- a/docs/oncore-shmem.txt
+++ b/docs/oncore-shmem.txt
@@ -38,9 +38,9 @@ this interface you must include a *STATUS* or *SHMEM* line in the
----------------------------
STATUS < file_name >
-
+
or
-
+
SHMEM < file_name >
----------------------------
=====================================
docs/parsedata.txt
=====================================
--- a/docs/parsedata.txt
+++ b/docs/parsedata.txt
@@ -2,7 +2,7 @@
The parse driver currently supports several clocks with different query
mechanisms. In order for you to find a sample that might be similar to a
-clock you might want to integrate into parse. I'll sum up the major
+clock you might want to integrate into parse, I'll sum up the major
features of the clocks (this information is distributed in the
parse/clk_*.c and ntpd/refclock_parse.c files).
@@ -22,12 +22,12 @@ have a pretty common output format in the stock version. In order to
support NTP Meinberg was so kind to produce some special versions of the
firmware for the use with NTP. So, if you are going to use a Meinberg
clock please ask whether there is a special Uni Erlangen version. You
-can reach http://www.meinberg.de/[Meinberg] via the Web. Information can
+can reach https://www.meinberg.de/[Meinberg] via the Web. Information can
also be ordered via eMail from
mailto:info at meinberg.de[]
General characteristics: +
-Meinberg clocks primarily output pulse per second and a describing
+Meinberg clocks primarily output one pulse per second and a describing
ASCII string. This string can be produced in two modes: either upon the
reception of a question mark or every second. NTP uses the latter
mechanism. DCF77 AM clocks have a limited accuracy of a few
@@ -48,7 +48,6 @@ The preferred tty setting for Meinberg DCF77 receivers is 9600/7E2:
IFLAG (IGNBRK|IGNPAR|ISTRIP)
OFLAG 0
LFLAG 0
-
--------------------------------------------------
The tty setting for Meinberg GPS16x/17x receivers is 19200/8N1:
@@ -58,7 +57,6 @@ The tty setting for Meinberg GPS16x/17x receivers is 19200/8N1:
IFLAG (IGNBRK|IGNPAR|ISTRIP)
OFLAG 0
LFLAG 0
-
---------------------------------------------------
All clocks should be run at datagram once per second. +
@@ -106,8 +104,8 @@ Format of the Uni Erlangen time string for PZF5xx receivers:
t = 'U' if UTC time is transmitted, else ' '
u = '#' for older PZF5xx receivers: no correlation, not synchronized
- '#' for PZF511 and newer: never synced since powerup
- ' ' if nothing of the above applies
+ '#' for PZF511 and newer: never synced since powerup
+ ' ' if none of the above applies
v = '*' if freewheeling based on internal quartz, else ' '
x = 'S' if daylight saving time is active, else ' '
y = '!' during the hour preceding start or end of daylight saving time, else ' '
@@ -163,7 +161,7 @@ codes, fixed format
direct DCF77 code input
-In Europe it is relatively easy/cheap the receive the german time code
+In Europe it is relatively easy/cheap to receive the German time code
transmitter DCF77. The simplest version to process its signal is to feed
the 100/200ms pulse of the demodulated AM signal via a level converter
to an RS232 port at 50Baud. parse/clk_rawdcf.c holds all necessary
@@ -238,7 +236,7 @@ encoding:
Schmid clock: needs poll, binary input, end='\xFC', sync start
The Schmid clock is a DCF77 receiver that sends a binary time code at
-the reception of a flag byte. The contents if the flag byte determined
+the reception of a flag byte. The contents of the flag byte determine
the time code format. The binary time code is delimited by the byte
0xFC.
@@ -334,7 +332,7 @@ GmbH, Department: ND250 A Joint venture of Daimler-Benz Aerospace and
Nortel.
--------------------------------------
- hopf Funkuhr 6021
+ hopf Funkuhr 6021
used with 9600,8N1,
UTC via serial line
"Sekundenvorlauf" ON
@@ -343,7 +341,6 @@ Nortel.
output time and date
transmit with control characters
transmit evry second
-
--------------------------------------
Type 6021 Serial Output format
@@ -359,7 +356,7 @@ Type 6021 Serial Output format
n = NL (0x0A), r = CR (0x0D)
A B - Status and weekday
-
+
A - Status
8 4 2 1
@@ -368,7 +365,7 @@ Type 6021 Serial Output format
x x 0 x - Wintertime
x x 1 x - Summertime
0 0 x x - Time/Date invalid
- 0 1 x x - Internal clock used
+ 0 1 x x - Internal clock used
1 0 x x - Radio clock
1 1 x x - Radio clock highprecision
@@ -392,20 +389,20 @@ The Computime receiver sends a datagram in the following format every
minute
------------------------------------------------------------
-
- Timestamp T:YY:MM:MD:WD:HH:MM:SSCRLF
+
+ Timestamp T:YY:MM:MD:WD:HH:MM:SSCRLF
Pos 0123456789012345678901 2 3
- 0000000000111111111122 2 2
+ 0000000000111111111122 2 2
Parse T: : : : : : : \r\n
-
- T Startcharacter "T" specifies start of the timestamp
- YY Year MM Month 1-12
- MD Day of the month
- WD Day of week
- HH Hour
- MM Minute
+
+ T Startcharacter "T" specifies start of the timestamp
+ YY Year MM Month 1-12
+ MD Day of the month
+ WD Day of week
+ HH Hour
+ MM Minute
SS Second
- CR Carriage return
+ CR Carriage return
LF Linefeed
------------------------------------------------------------
@@ -419,23 +416,23 @@ set up the clock to send a datagram every second. For use with this
driver, the WHARTON 400A Series clock must be set-up as follows :
--------------------------------------------
- Programmable Selected
- Option No Option
- BST or CET display 3 9 or 11
- No external controller 7 0
- Serial Output Format 1 9 1
- Baud rate 9600 bps 10 96
- Bit length 8 bits 11 8
- Parity even 12 E
+ Programmable Selected
+ Option No Option
+ BST or CET display 3 9 or 11
+ No external controller 7 0
+ Serial Output Format 1 9 1
+ Baud rate 9600 bps 10 96
+ Bit length 8 bits 11 8
+ Parity even 12 E
--------------------------------------------
WHARTON 400A Series output format 1 is as follows :
--------------------------------------------------------------
Timestamp STXssmmhhDDMMYYSETX
- Pos 0 12345678901234
- 0 00000000011111
-
+ Pos 0 12345678901234
+ 0 00000000011111
+
STX start transmission (ASCII 0x02)
ETX end transmission (ASCII 0x03)
ss Second expressed in reversed decimal (units then tens)
=====================================
docs/quick.txt
=====================================
--- a/docs/quick.txt
+++ b/docs/quick.txt
@@ -76,7 +76,7 @@ filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
-logfile /var/log/ntpd.log
+logfile /var/log/ntpd.log
logconfig =syncall +clockall +peerall +sysall
------------------------------------------------------------------
@@ -86,9 +86,9 @@ diagnostics useful for tuning your time service.
Your security/access section will almost always look a lot like this:
------------------------------------------------------------------
-restrict default kod limited nomodify nopeer noquery
+restrict default kod limited nomodify nopeer noquery
restrict -6 default kod limited nomodify nopeer noquery
-restrict 127.0.0.1
+restrict 127.0.0.1
restrict -6 ::1
------------------------------------------------------------------
@@ -221,7 +221,7 @@ HOWTO].
[[dhcp]]
== Special considerations when using DHCP ==
-If your machine uses DHCP to get a dynamic IP address from your ISP,
+If your machine uses DHCP to get a dynamic IP address from 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
=====================================
docs/rdebug.txt
=====================================
--- a/docs/rdebug.txt
+++ b/docs/rdebug.txt
@@ -11,7 +11,7 @@ Call the girls and they'll sweep your bugs.
== Related Links ==
-include::includes/refclock.txt[]
+include::includes/refclock.txt[]
include::includes/install.txt[]
'''''
=====================================
docs/tf582_4.txt
=====================================
--- a/docs/tf582_4.txt
+++ b/docs/tf582_4.txt
@@ -1,13 +1,13 @@
= European Automated Computer Time Services =
The National Laboratories of many European countries provide
-time information in a standardised format, an ITU-R
+time information in a standardised format, an ITU-R
Recommendation (ITU-R TF583.4). Information is provided
over a dial-up modem, with one 78-char segment every second.
A description of the time code is available at
https://www.ptb.de/cms/en/ptb/fachabteilungen/abt4/fb-44/ag-442/dissemination-of-legal-time/dissemination-of-time-via-the-public-telephone-network/the-european-telephone-time-code.html
-The following countries have traditionally provided this service:
+The following countries have traditionally provided this service:
Austria, Belgium, Germany, Italy, The Netherlands, Poland, Portugal,
Romania, Spain, Sweden, Switzerland, Turkey and United Kingdom.
=====================================
ntpd/ntp.conf-man.txt
=====================================
--- a/ntpd/ntp.conf-man.txt
+++ b/ntpd/ntp.conf-man.txt
@@ -61,8 +61,7 @@ some weird and even destructive behavior.
In contexts where a host name is expected, a `-4`or `--ipv4`
qualifier preceding the host name forces DNS resolution to the IPv4
namespace, while a `-6` or `--ipv6' qualifier forces DNS resolution to
-the IPv6 namespace. See IPv6 references for the equivalent classes for
-that address family.
+the IPv6 namespace.
include::../docs/includes/assoc-commands.txt[]
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/d1629e4e43bb0ad28369960229065ec4586e5d64...3981d852992961b30df60e35df3da40c07c79bc5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20161225/5bef776c/attachment.html>
More information about the vc
mailing list