[Git][NTPsec/ntpsec][master] 2 commits: Typos, doc tweaks

Hal Murray gitlab at mg.gitlab.com
Sat Oct 19 22:15:38 UTC 2019



Hal Murray pushed to branch master at NTPsec / ntpsec


Commits:
865f7a96 by Hal Murray at 2019-10-10T07:27:24Z
Typos, doc tweaks

- - - - -
9f726c30 by Hal Murray at 2019-10-17T11:37:10Z
Repair time-since-reset (column 3) in usestats

- - - - -


4 changed files:

- devel/linkcheck
- docs/standards.adoc
- ntpd/ntp_proto.c
- ntpd/ntp_util.c


Changes:

=====================================
devel/linkcheck
=====================================
@@ -7,7 +7,7 @@
 # mode.
 #
 # Optional argument is the root directory of the tree, otherwise it
-# is run from the corrent directory.
+# is run from the current directory.
 #
 # SPDX-License-Identifier: BSD-2-Clause
 from __future__ import print_function, division


=====================================
docs/standards.adoc
=====================================
@@ -18,11 +18,11 @@ SNTP is specified by link:https://tools.ietf.org/html/rfc2030[RFC 2030:
 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI].
 
 Extension fields are described by
-link:https://tools.ietf.org/html/rfc5905[RFC 7822: Network Time Protocol
+link:https://tools.ietf.org/html/rfc7822[RFC 7822: Network Time Protocol
 Version 4 (NTPv4) Extension Fields].
 
 NTPsec has entirely dropped conformance with the Autokey feature
-described in link:https://tools.ietf.org/html/rfc5905[RFC 5906].  Autokey
+described in link:https://tools.ietf.org/html/rfc5906[RFC 5906].  Autokey
 never quite worked, and the design was unstable enough that if there
 was ever actually a time when it fully conformed to its RFC that span
 must have been pretty short.
@@ -60,9 +60,9 @@ link:https://datatracker.ietf.org/doc/draft-ietf-ntp-data-minimization/[NTP
 Client Data Minimization] draft RFC, which changes the client-side
 generation of some packet headers.
 
-NTPsec also conforms to the
-link:https://datatracker.ietf.org/doc/draft-ietf-ntp-mac/[MAC for NTP]
-draft RFC, implementing AES-CMAC (128 bits).
+NTPsec also implements
+link:https://tools.ietf.org/html/rfc8573[RFC 8573:
+Message Authentication Code for the Network Time Protocol].
 
 The table of reference identifiers in Figure 12 is largely obsolete
 and somewhat incomplete relative to the code.


=====================================
ntpd/ntp_proto.c
=====================================
@@ -223,11 +223,11 @@ uint64_t stat_kodsent(void)
 
 uptime_t stat_use_stattime(void)
 {
-  return stat_count.sys_stattime;
+  return stat_count.use_stattime;
 }
 
 void set_use_stattime(uptime_t stattime) {
-  stat_count.sys_stattime = stattime;
+  stat_count.use_stattime = stattime;
 }
 
 


=====================================
ntpd/ntp_util.c
=====================================
@@ -634,7 +634,7 @@ void record_use_stats(void)
 		stimex += usage.ru_stime.tv_sec -  oldusage.ru_stime.tv_sec;
 		fprintf(usestats.fp,
 		    "%s %u %.3f %.3f %ld %ld %ld %ld %ld %ld %ld %ld %ld\n",
-		    timespec_to_MJDtime(&now), current_time - stat_stattime(),
+		    timespec_to_MJDtime(&now), current_time - stat_use_stattime(),
 		    utime, stimex,
 		    usage.ru_minflt -   oldusage.ru_minflt,
 		    usage.ru_majflt -   oldusage.ru_majflt,



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/519b1fe0e2510889008e1a275ca3c012ecf8b31e...9f726c3076bc954cdb2549095e6a003414fc8306

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/519b1fe0e2510889008e1a275ca3c012ecf8b31e...9f726c3076bc954cdb2549095e6a003414fc8306
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/20191019/09a3f6d6/attachment-0001.htm>


More information about the vc mailing list