[Git][NTPsec/ntpsec][master] 11 commits: Capitalize HTML
Eric S. Raymond
gitlab at mg.gitlab.com
Sun Dec 18 09:49:22 UTC 2016
Eric S. Raymond pushed to branch master at NTPsec / ntpsec
Commits:
00dadd84 by Richard Laager at 2016-12-18T00:47:28-05:00
Capitalize HTML
- - - - -
8b0d3430 by Richard Laager at 2016-12-18T00:47:28-05:00
Fix a typo
- - - - -
e86d0ac7 by Richard Laager at 2016-12-18T00:47:28-05:00
Fix a typo
- - - - -
f8ab28a6 by Richard Laager at 2016-12-18T00:47:28-05:00
Fix a duplicated slash
- - - - -
be1b9212 by Richard Laager at 2016-12-18T00:47:28-05:00
Make the ntpviz examples more consistent
This makes the headers consistent on all three pages, such that clicking
between them is as seamless as possible (given that index.html is not
generated and so cannot show the hostname).
- - - - -
be3bc17f by Richard Laager at 2016-12-18T00:47:28-05:00
Make seccomp_init() error messages consistent
- - - - -
eaed7486 by Sanjeev Gupta at 2016-12-18T00:48:41-05:00
Correct count mistake
- - - - -
367cc046 by Sanjeev Gupta at 2016-12-18T00:48:41-05:00
Reorder sentences in Broadcast paragraphs
The antecedent for "these" was wrong
- - - - -
1d8c3e19 by Sanjeev Gupta at 2016-12-18T00:48:41-05:00
Add mcast description in summary
This had probably been removed wrongly at some time,
mcast server is still supported
- - - - -
a545a62d by Sanjeev Gupta at 2016-12-18T00:48:41-05:00
Distinguish use case between manycast and broadcast
- - - - -
62564b05 by Sanjeev Gupta at 2016-12-18T00:48:41-05:00
Expand use of pool command
Distinguishing it from server command
- - - - -
8 changed files:
- docs/discover.txt
- docs/includes/misc-options.txt
- docs/includes/ntpd-body.txt
- docs/includes/ntpviz-body.txt
- ntpd/ntp_sandbox.c
- www/day/header
- www/index.html
- www/week/header
Changes:
=====================================
docs/discover.txt
=====================================
--- a/docs/discover.txt
+++ b/docs/discover.txt
@@ -26,11 +26,13 @@ include::includes/hand.txt[]
== Introduction ==
This page describes the automatic server discovery schemes provided in
-NTPv4. There are two automatic server discovery schemes: broadcast and
-server pool, which are described on this page. The broadcast scheme
-utilizes the ubiquitous broadcast or one-to-many paradigm native to
-IPv4 and IPv6. The server pool scheme uses DNS to resolve addresses
-of multiple volunteer servers scattered throughout the world.
+NTPv4. There are three automatic server discovery schemes: broadcast,
+manycast, and server pool; which are described on this page. The
+broadcast scheme utilizes the ubiquitous broadcast or one-to-many
+paradigm native to IPv4 and IPv6. The manycast scheme is similar
+to specifying to broadcast, but the servers listen on a specific
+address known to the client. The server pool scheme uses DNS to resolve
+addresses of multiple volunteer servers scattered throughout the world.
All three schemes work in much the same way and might be described as
_grab-n'-prune._ Through one means or another they grab a number of
@@ -101,13 +103,15 @@ results in a volley of six client/server exchanges at 2-s intervals
during which both the synchronization and cryptographic protocols run
concurrently.
-Following the volley, the server continues in listen-only mode and sends
-no further messages. If for some reason the broadcast server does not
+If for some reason the broadcast server does not
respond to these messages, the client will cease transmission and
continue in listen-only mode with a default propagation delay. The
volley can be avoided by using the +broadcastdelay+ command with nonzero
argument.
+Following the volley, the server continues in listen-only mode and sends
+no further messages for this association.
+
A server is configured in broadcast mode using the +broadcast+ command
and specifying the broadcast address of a local interface. If two or
more local interfaces are installed with different broadcast addresses,
@@ -133,7 +137,8 @@ release.
Manycast is an automatic server discovery and configuration paradigm.
It is intended as a means for a client to troll the nearby network
-neighborhood to find cooperating servers, validate them using
+neighborhood (not necessarily on the same link, where broadcast
+would work), to find cooperating servers, validate them using
cryptographic means and evaluate their time values with respect to
other servers that might be lurking in the vicinity. It uses the
grab-n'-drop paradigm with the additional feature that active means
@@ -162,7 +167,8 @@ unicast server message.
== Server Pool Scheme ==
The idea of targeting servers on a random basis to distribute and
-balance the load is not a new one; however, the NTP pool scheme puts
+balance the load is not a new one; however, the
+http://www.pool.ntp.org/en/use.html[NTP Pool Project] puts
this on steroids. At present, several thousand operators around the
globe have volunteered their servers for public access. In general,
NTP is a lightweight service and servers used for other purposes don't
@@ -172,21 +178,22 @@ advantages of multiple servers using the NTP mitigation algorithms.
To support this service, custom DNS software is used by pool.ntp.org
and its subdomains to discover a random selection of participating
-servers in response to a DNS query. The client receiving this list
-mobilizes some or all of them, similar to the manycast discovery
-scheme, and prunes the excess. Cryptographic authentication is not
-required.
+(in-country) servers in response to a DNS query. The client receiving
+this list mobilizes some or all of them, similar to the manycast
+discovery scheme, and prunes the excess. Cryptographic authentication
+is not required.
The pool scheme is configured using one or more +pool+ commands with DNS
names indicating the pool from which to draw. The +pool+ command can be
used more than once; duplicate servers are detected and discarded. In
principle, it is possible to use a configuration file containing a
-single line +pool pool.ntp.org+. The
-http://www.pool.ntp.org/en/use.html[NTP Pool Project] offers
+single line +pool pool.ntp.org+. The NTP Pool Project offers
instructions on using the pool with the +server+ command, which is
suboptimal but works with older versions of +ntpd+ predating the +pool+
-command. Consider replacing the multiple +server+
-commands in their example with a single +pool+ command.
+command. Use of the +server+ command does a one-time DNS lookup, and
+uses the IP address returned thereafter. If the server becomes unavailable,
+the DNS will not be re-resolved. The +pool+ command will
+use multiple servers that the DNS resolves to, refreshing as required.
'''''
=====================================
docs/includes/misc-options.txt
=====================================
--- a/docs/includes/misc-options.txt
+++ b/docs/includes/misc-options.txt
@@ -138,7 +138,7 @@ and so on is suppressed.
+logfile+ _logfile_::
This command specifies the location of an alternate log file to be
- used instead of the default system _syslog_(3)_ facility. This is the
+ used instead of the default system _syslog(3)_ facility. This is the
same operation as the -l command line option.
[[mru]]
=====================================
docs/includes/ntpd-body.txt
=====================================
--- a/docs/includes/ntpd-body.txt
+++ b/docs/includes/ntpd-body.txt
@@ -381,7 +381,7 @@ synchronized and stable.
Finally, if you have processes like _dovecot_ or database servers that
require monotonically-increasing time, run {ntpwaitman} as
-late as possible in the boot sequence (perhaps with the_+-v+_flag) and
+late as possible in the boot sequence (perhaps with the +-v+ flag) and
after {ntpwaitman} exits successfully it is as safe as it
will ever be to start any process that require stable time.
=====================================
docs/includes/ntpviz-body.txt
=====================================
--- a/docs/includes/ntpviz-body.txt
+++ b/docs/includes/ntpviz-body.txt
@@ -161,7 +161,7 @@ are generated into the output directory.
When an index is generated, ntpviz will look for two files in the
output directory. Neither of these files need be present, and the
-'header' and 'footer' files may contain arbitrary html.
+'header' and 'footer' files may contain arbitrary HTML.
The first file is named 'header'. The contents of that file will be
added almost at the top of the body on the generated index page.
=====================================
ntpd/ntp_sandbox.c
=====================================
--- a/ntpd/ntp_sandbox.c
+++ b/ntpd/ntp_sandbox.c
@@ -279,11 +279,11 @@ getgroup:
if (NULL == ctx) {
- msyslog(LOG_ERR, "sandbox: seccomp_init failed: %m");
+ msyslog(LOG_ERR, "sandbox: seccomp_init() failed: %m");
return nonroot;
}
else
- msyslog(LOG_DEBUG, "sandbox: seccomp_init succeeded");
+ msyslog(LOG_DEBUG, "sandbox: seccomp_init() succeeded");
int scmp_sc[] = {
SCMP_SYS(adjtimex),
=====================================
www/day/header
=====================================
--- a/www/day/header
+++ b/www/day/header
@@ -1,5 +1,5 @@
<!-- You may customize your top of page nav here. -->
<a href="../index.html">Top</a>
-<a href="../day/index.html">Daily stats</a>
-<a href="..//week/index.html">Weekly stats</a>
+Daily Stats
+<a href="../week/index.html">Weekly Stats</a>
<br><br>
=====================================
www/index.html
=====================================
--- a/www/index.html
+++ b/www/index.html
@@ -1,22 +1,29 @@
<!DOCTYPE html>
<html>
<head>
+<link rel="shortcut icon" href="favicon.ico">
+<meta charset="UTF-8">
<title>ntpviz</title>
-<link rel="icon" type="image/ico" href="favicon.ico">
-<meta http-equiv="refresh" content="1800">
-<meta charset="utf-8">
</head>
<body>
-<img src="ntpsec-logo.png"
- style="float:left;margin:5px 50px 10px 50px;">
+<div style="width:910px">
+<a href='https://www.ntpsec.org/'>
+<img src="ntpsec-logo.png" alt="NTPsec" style="float:left;margin:20px 70px;">
+</a>
<div>
-<h1>ntpviz</h1>
+<h1 style="margin-bottom:10px;">ntpviz</h1>
+<br>
+<br>
<br>
<br>
-<a href="day/index.html">Daily Stats</a>
-<a href="week/index.html">Weekly Stats</a>
</div>
-<div style="clear:both;" />
+<div style="clear:both;"></div><br>
+<!-- You may customize your top of page nav here. -->
+Top
+<a href="day/index.html">Daily stats</a>
+<a href="week/index.html">Weekly stats</a>
+<br><br>
+
<div> You may customize this top level index file to your taste.
You may wish to describe your system here, show contact
information, or add a link to your running ntp.conf.</div>
=====================================
www/week/header
=====================================
--- a/www/week/header
+++ b/www/week/header
@@ -1,5 +1,5 @@
<!-- You may customize your top of page nav here. -->
<a href="../index.html">Top</a>
-<a href="../day/index.html">Daily stats</a>
-<a href="../week/index.html">Weekly stats</a>
+<a href="../day/index.html">Daily Stats</a>
+Weekly Stats
<br><br>
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/30e3000a9b6e1dfb3cb7aa0c51a3ddc6dff93c52...62564b05a8da0687a06da85010ca79218cd63fa3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20161218/ab5ad310/attachment.html>
More information about the vc
mailing list