[Git][NTPsec/ntpsec][master] 2 commits: docs/includes/misc-options.txt: explain usage of rlimit memlock -1

Sun May 29 15:27:46 UTC 2016

Eric S. Raymond pushed to branch master at NTPsec / ntpsec


Commits:
2f75dc73 by Kenyon Ralph at 2016-05-29T11:27:20-04:00
docs/includes/misc-options.txt: explain usage of rlimit memlock -1

- - - - -
95ff581f by Eric S. Raymond at 2016-05-29T11:27:20-04:00
Documentation and TODO updates.

- - - - -


5 changed files:

- devel/TODO
- docs/driver31.txt
- docs/includes/misc-options.txt
- docs/includes/ntpd-body.txt
- ntpd/refclock_jupiter.c


Changes:

=====================================
devel/TODO
=====================================

--- a/devel/TODO
+++ b/devel/TODO
@@ -37,8 +37,15 @@
 * systime.c needs patching to put ntpdsim's hook back in place. Deferred
   until the ntpdsim build is fixed.
 
-* Hal has seen a core dump in ntpdig.  It has not reproduced, so we don't
-  know what's going on there.
+* Can the KERNEL_PLL code be removed? It's used by drivers 4, 8, 20, 22, and
+  30, but Hal thinks it may no longer have a point since processors are much
+  faster and schedulers smoother than whem it was built.  Might remove the
+  need for adjtimex(2). We need to collect statistics on builds with and
+  without the PLL to see if it's actually a win.
+
+* From refclock_params in ntpd/ntp_refclock.c: " FreeBSD serial ports
+  provide capture on the clear edge, while FreeBSD parallel ports
+  provide capture on the assert edge.: Needs checking.
 
 === Testing ===
 
@@ -59,8 +66,6 @@
 * Short doc on how to tell your ntpd is running correctly.
   Perhaps lifted from GPSD Time Service HOWTO?
 
-* The format and organization of the NEWS file needs a rethink.
-
 == After 1.0 release ==
 
 === Slow convergence ===
@@ -155,9 +160,7 @@ Neither is ideal, easy pickings for someone to code on.
   codes and use it systematically to make reports more readable.
 
 * Timer events need, as much as possible, to be eliminated - they eat
-  power on laptops and mobile devices, usually unnecessarily.  At least
-  one, the /etc/resolv.conf reload, would be better handled under Linux
-  by asynchronous file-change notifications.
+  power on laptops and mobile devices, usually unnecessarily.
 
 * Take another look at SHM.  Hal thinks we can make a version that is
   read-only and solid.  Maybe write a support package that does all the


=====================================
docs/driver31.txt
=====================================
--- a/docs/driver31.txt
+++ b/docs/driver31.txt
@@ -89,7 +89,7 @@ http://www.gpskit.nl/documents/rockwell/jupiter-gps-board.pdf[GPSKit.nl]
 
 === Configuration ===
 
-The edge of the PPS signal that is on-time can be set with +flag2+.
+The edge of the PPS signal that is on-time can be set with +flag3+.
 There is currently no way to cause the +PPS+ signal to control the
 kernel +PLL+.
 


=====================================
docs/includes/misc-options.txt
=====================================
--- a/docs/includes/misc-options.txt
+++ b/docs/includes/misc-options.txt
@@ -282,10 +282,13 @@ The variables operate as follows:
 +rlimit+ [+memlock+ _megabytes_ | +stacksize+ _4kPages_ | +filenum+ _filedescriptors_]::
 
   +memlock+ _megabytes_;;
-    Specify the number of megabytes of memory that can be allocated.
-    Probably only available under Linux, this option is useful when
-    dropping root (the +-i+ option). The default is 32 megabytes.
-    Setting this to zero will prevent any attempt to lock memory.
+    Specify the number of megabytes of memory that should be allocated
+    and locked.  Probably only available under Linux, this option may
+    be useful when dropping root (the <tt>-i</tt> option).  The
+    default is 32 megabytes on non-Linux machines, and -1 under Linux.
+    -1 means "do not lock the process into memory".  0 means "lock
+    whatever memory the process wants into memory". -1 means "don't
+    use locked memory".
   +stacksize+ _4kPages_;;
     Specifies the maximum size of the process stack on systems with the
     mlockall()_function. Defaults to 50 4k pages (200 4k pages in OpenBSD).


=====================================
docs/includes/ntpd-body.txt
=====================================
--- a/docs/includes/ntpd-body.txt
+++ b/docs/includes/ntpd-body.txt
@@ -116,7 +116,7 @@ This is the same operation as the _driftfile_
 configuration specification in the +/etc/{ntpconf}+ file.
 
 +-g+, +--panicgate+::
-  Allow the first adjustment to be Big. This option may appear an
+  Allow the first adjustment to be big. This option may appear an
   unlimited number of times.
 +
 Normally, +{ntpd}+ exits with a message to the system log if the offset


=====================================
ntpd/refclock_jupiter.c
=====================================
--- a/ntpd/refclock_jupiter.c
+++ b/ntpd/refclock_jupiter.c
@@ -32,14 +32,8 @@
 #endif
 
 /*
- * This driver supports the Rockwell Jupiter GPS Receiver board
- * adapted to precision timing applications.  It requires the PPS API
- * support. It also requires a gadget box and 1-PPS level converter,
- * such as described in the Pulse-per-second (PPS) Signal Interfacing
- * page.
- *
- * It may work (with minor modifications) with other Rockwell GPS
- * receivers such as the CityTracker.
+ * This driver supports the Rockwell Jupiter GPS engine.
+ * It requires the PPS API support.
  */
 
 /*



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/ff92f04bd1277363a7d5687ef3918a9e54d8234d...95ff581f9814eb1294db9dc71acb6c8d9d3c173b
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20160529/dad45b69/attachment.html>
