[Git][NTPsec/ntpsec][master] 4 commits: Remove extra semicolon outside of a function.
Eric S. Raymond
gitlab at mg.gitlab.com
Thu Feb 25 05:31:25 UTC 2016
Eric S. Raymond pushed to branch master at NTPsec / ntpsec
Commits:
9419cb6d by Matt Selsky at 2016-02-25T00:29:05-05:00
Remove extra semicolon outside of a function.
- - - - -
09afc94d by Sanjeev Gupta at 2016-02-25T00:29:58-05:00
Work through FIXME in docs, updating markup and links
- - - - -
a44fd86f by Sanjeev Gupta at 2016-02-25T00:31:02-05:00
Document potential removal of some driver8 (PARSE) modes
- - - - -
8b2e6803 by Sanjeev Gupta at 2016-02-25T00:31:02-05:00
Add note on Mode 3 and 4 in refclock_parse.c
- - - - -
10 changed files:
- docs/authentic.txt
- docs/driver20.txt
- docs/driver30.txt
- docs/driver8.txt
- docs/driver9.txt
- docs/filter.txt
- docs/index.txt
- docs/rate.txt
- libntp/authkeys.c
- ntpd/refclock_parse.c
Changes:
=====================================
docs/authentic.txt
=====================================
--- a/docs/authentic.txt
+++ b/docs/authentic.txt
@@ -164,7 +164,7 @@ selects the key used as the password for the {ntpqman} utility.
//strong security against replay with or without modification, spoofing,
//masquerade and most forms of clogging attacks.
//
-////FIXME: page reference may be invalid
+//FIXME: page reference may be invalid
//The Autokey protocol has several modes of operation corresponding to
//the various NTP modes supported. Most modes use a special cookie which
//can be computed independently by the client and server, but encrypted
=====================================
docs/driver20.txt
=====================================
--- a/docs/driver20.txt
+++ b/docs/driver20.txt
@@ -49,7 +49,6 @@ The various GPS sentences that this driver recognises look like this:
|$GPZDG,GPSTIME,DD,MM,YYYY,AA.BB,V*CS<cr><lf>|Accord
|=============================================================================
-//FIXME: 'GPS sync status' in table not indented properly
.NMEA data items
[cols="15%,85%",options="header"]
[options="header"]
@@ -185,7 +184,6 @@ example:
Sentences like $GPGSV that don't contain the time will get counted in
the total but otherwise ignored.
-//FIXME: ntp.org reference
http://support.ntp.org/bin/view/Support/ConfiguringNMEARefclocks[Configuring
NMEA Refclocks] might give further useful hints for specific hardware
devices that exhibit strange or curious behaviour.
=====================================
docs/driver30.txt
=====================================
--- a/docs/driver30.txt
+++ b/docs/driver30.txt
@@ -11,7 +11,7 @@ PPS Port: /dev/oncore.pps._u_
== Description ==
This driver supports most models of the
-http://www.mot.com/AECS/PNSB/products[Motorola Oncore GPS receivers]
+https://web.archive.org/web/19990427102123/http://www.mot.com/AECS/PNSB/products/produt.html[Motorola Oncore GPS receivers]
(Basic, PVT6, VP, UT, UT+, GT, GT+, SL, M12, M12+T), as long as they
support the _Motorola Binary Protocol_.
@@ -21,7 +21,7 @@ available new, and the UT, GT, and SL are at end-of-life. The Motorola
evaluation kit can be recommended. It interfaces to a PC straightaway,
using the serial (DCD) or parallel port for PPS input and packs the
receiver in a nice and sturdy box. Less expensive interface kits are
-available from http://www.tapr.org[TAPR] and
+available from http://www.tapr.org[TAPR].
[width="100%",cols="<34%,<33%,<33%",align="center",frame="none",grid="none"]
|==========================================================================
@@ -84,10 +84,9 @@ on Linux, SunOS and Solaris.
=== Configuration ===
-//FIXME: Ignored backticks around ntp.oncore
There is a driver specific configuration file +ntp.oncore+ (or
-+ntp.oncore.+_u_ or +ntp.oncore+_u_ if you must distinguish between more
-than one Oncore receiver) that contains information on the startup mode,
++ntp.oncore.+'u' or +ntp.oncore+'u' if you must distinguish between more
+than one Oncore receiver _unit_) that contains information on the startup mode,
the location of the GPS receiver, an offset of the PPS signal from zero,
and the cable delay. The offset shifts the PPS signal to avoid interrupt
pileups +on' the second, and adjusts the timestamp accordingly. See the
@@ -109,8 +108,8 @@ factor will be the timebase of the computer and the precision with which
you can timestamp the rising flank of the PPS signal. Using FreeBSD, a
FPGA based Timecounter/PPS interface, and an ovenized quartz oscillator,
that performance has been reproduced. For more details on this aspect:
-http://phk.freebsd.dk/rover.html[Sub-Microsecond timekeeping under
-FreeBSD].
+https://web.archive.org/web/19990221121441/http://phk.freebsd.dk/rover.html[Sub-Microsecond
+timekeeping under FreeBSD].
'''''
=====================================
docs/driver8.txt
=====================================
--- a/docs/driver8.txt
+++ b/docs/driver8.txt
@@ -14,9 +14,15 @@ PPS device: /dev/refclockpps-'u'; alternate PPS device
== Description ==
-The PARSE driver supports 20 different clock
+The PARSE driver supports 25 different clock
types/configurations. PARSE is actually a multi-clock driver.
+Note that some of these modes below are to support equipment that
+has not been commercially available for a long time; and may be
+removed. See
+https://www.ntpsec.org/removal-plan.html[Feature removals] for a
+discussion of this issue.
+
The actual receiver status is mapped into various synchronization states
generally used by receivers. The driver is configured to interpret the
time codes of Meinberg DCF77 AM receivers, DCF77 FM receivers, Meinberg
@@ -66,9 +72,10 @@ refclock_ppstime::
== Supported Devices ==
-Currently, twenty-four clock types are supported by the PARSE driver and
+Currently, twenty-five clock types are supported by the PARSE driver and
up to four (devices /dev/refclock-0 - /dev/refclock-3) of these clocks
may be operational at any one time.
+
A note on the implementations:
* These implementations were mainly done without actual access to the
@@ -104,17 +111,23 @@ This implementation was provided and verified by SEL and
http://networktimefoundation.org[Network Time Foundation] has an
SEL-2407 in one of its development labs.
-The pictures below have been taken from and are linked to the vendors'
-web pages.
+The pictures below have been archived from the vendors' web pages.
* *server 127.127.8.0-3 mode 0*
+
-*http://www.meinberg.de[Meinberg] http://www.meinberg.de/english/products/timesource.htm#dcf---freq_sync[PZF5xx receiver family] (FM demodulation/TCXO / 50μs)*
-
+*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:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
* *server 127.127.8.0-3 mode 1*
+
-*http://www.meinberg.de[Meinberg] http://www.meinberg.de/english/products/timesource.htm#dcf---freq_sync[PZF5xx receiver family] (FM demodulation/OCXO / 50μs)*
+*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:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
image::pic/pzf511.jpg[http://www.meinberg.de/english/products/pzf-eurocard.htm]
@@ -140,10 +153,18 @@ that comes with the Meinberg driver package.
* *server 127.127.8.0-3 mode 3*
+
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:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
* *server 127.127.8.0-3 mode 4*
+
*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:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
* *server 127.127.8.0-3 mode 5*
+
@@ -182,11 +203,19 @@ image:pic/igclock.gif[http://www.igel.de/eigelmn.html]
* *server 127.127.8.0-3 mode 9*
+
*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:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
* *server 127.127.8.0-3 mode 10*
+
*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:
+https://www.ntpsec.org/removal-plan.html[Feature removals]
++
image:pic/pd_om011.gif[http://www.trimble.com/cgi/omprod.cgi/pd_om011.html]
+
image:pic/pd_om006.gif[http://www.trimble.com/cgi/omprod.cgi/pd_om006.html]
=====================================
docs/driver9.txt
=====================================
--- a/docs/driver9.txt
+++ b/docs/driver9.txt
@@ -21,11 +21,11 @@ precision timing applications. This driver supports all compatible
receivers such as the 6-channel MX4200, MX4200D, and the 12-channel
MX9212, MX9012R, MX9112.
-//FIXME: caption and float attributes not showing up correctly
-image:pic/9400n.jpg["MX9400N",float="left",link="http://www.leica-gps.com/", caption="Leica MX9400N Navigator"] http://www.leica-gps.com/[Leica Geosystems] acquired the
-Magnavox commercial GPS technology business in February of 1994. They
-now market and support former Magnavox GPS products such as the MX4200
-and its successors.
+image:pic/9400n.jpg["MX9400N",float="left",caption="Leica MX9400N Navigator"]
+https://web.archive.org/web/19971014210945/http://www.leica-gps.com/[Leica
+Geosystems] acquired the Magnavox commercial GPS technology business in
+February of 1994. They marketed and supported former Magnavox GPS
+products such as the MX4200 and its successors.
== Operating Modes ==
=====================================
docs/filter.txt
=====================================
--- a/docs/filter.txt
+++ b/docs/filter.txt
@@ -72,8 +72,7 @@ process inserts a dummy infinity sample in the shift register for each
poll sent. After eight polls, the register returns to its original
state.
-//FIXME: Image pair not centered
-image:pic/flt1.gif[] image:pic/flt2.gif[]
+image:pic/flt1.gif["Raw",align="left"] image:pic/flt2.gif["Filtered",align="right"]
Figure 2. Raw (left) and Filtered (right) Offsets
=====================================
docs/index.txt
=====================================
--- a/docs/index.txt
+++ b/docs/index.txt
@@ -161,7 +161,7 @@ link:rate.html[Rate Management]::
Describes the principles of rate management to minimize network load
and defend against DoS attacks.
link:refclock.html[Reference Clock Support]::
- Describes the collection of radio clocks used to synchronize primary
+ Describes the collection of clocks and devices used to synchronize primary
servers.
link:warp.html[How NTP Works]::
Gives an overview of the NTP daemon architecture and how it works.
=====================================
docs/rate.txt
=====================================
--- a/docs/rate.txt
+++ b/docs/rate.txt
@@ -36,10 +36,17 @@ that can clog the server and network infrastructure. On the other hand,
friendly clients need to avoid configurations that can result in
unfriendly behavior.
-//FIXME: add footnote ref.
A review of past client abuse incidence shows the most frequent scenario
is a broken client that attempts to send packets at rates of one per
-second or more. On one occasion due to a defective client design [1],
+second or more. On one occasion due to a defective client design
+footnote:[1. Mills, D.L., J. Levine, R. Schmidt and D. Plonka. Coping with
+overload on the Network Time Protocol public servers. _Proc. Precision
+Time and Time Interval (PTTI) Applications and Planning Meeting_
+(Washington DC, December 2004), 5-16. Paper:
+{millshome}database/papers/ptti/ptti04a.pdf[PDF],
+Slides:{millshome}database/brief/ptti/ptti04.pdf[PDF]
+|
+{millshome}database/brief/ptti/ptti04.ppt[PowerPoint]]
over 750,000 clients demonstrated this abuse. There have been occasions
where this abuse has persisted for days at a time. These scenarios are
the most damaging, as they can threaten not only the victim server but
=====================================
libntp/authkeys.c
=====================================
--- a/libntp/authkeys.c
+++ b/libntp/authkeys.c
@@ -55,7 +55,7 @@ static void freesymkey(symkey *, symkey **);
static void free_auth_mem(void);
#endif
-symkey key_listhead; /* list of all in-use keys */;
+symkey key_listhead; /* list of all in-use keys */
/*
* The hash table. This is indexed by the low order bits of the
* keyid. This gets updated in auth_resize_hashtable
=====================================
ntpd/refclock_parse.c
=====================================
--- a/ntpd/refclock_parse.c
+++ b/ntpd/refclock_parse.c
@@ -13,6 +13,8 @@
* next time this code gets serious attention. In particular, modes 9 and 10
* support the Trimble SVeeSix, which was discontinued before 2003. Related
* code in the parse library could also be dropped.
+ * Also see modes 3 and 4, for which no information in use since 1999 and
+ * 2001 respectively can be found on the web.
*/
#include "config.h"
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/3a0c138910dbf11588313ae1862c5dd6a73e203b...8b2e68035359ca0b717ffb620562ffe9100154c1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20160225/eafd4e0b/attachment.html>
More information about the vc
mailing list