From: Juergen Perlinger Date: Thu, 14 Apr 2022 06:07:58 +0000 (+0200) Subject: [Bug 3758] Provide a 'device' config statement for refclocks X-Git-Tag: NTP_4_2_8P16~62^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=225215dabf289719397958ab078fe6b7e4da5265;p=thirdparty%2Fntp.git [Bug 3758] Provide a 'device' config statement for refclocks - update docs on refclock-gpsdjson bk: 6257ba3efyMkjCiFr-uXToTq167c0g --- diff --git a/html/drivers/driver46.html b/html/drivers/driver46.html index cdb0b6899..f0eb9cf07 100644 --- a/html/drivers/driver46.html +++ b/html/drivers/driver46.html @@ -92,11 +92,11 @@

Naming a Device

- The GPSD driver uses the same device name as the NMEA - driver, namely /dev/gpsu. There is a simple - reason for that: While the NMEA driver and the GPSD - driver can be active at the same time for different - devices, they cannot access the same device at a + By default, the GPSD driver uses the same device name as + the NMEA driver, namely /dev/gpsu. There is a + simple reason for that: While the NMEA driver and + the GPSD driver can be active at the same time for + different devices, they cannot access the same device at a time. Having the same name helps on that. It also eases migration from using NMEA directly to using GPSD, as no new links etc need to be created. @@ -110,11 +110,18 @@ identification. This makes the migration from the built-in NMEA driver a bit easier.

+

+ The driver also honors device statements for + the timedata channel. (PPS is handled + inside GPSD, so there's no need for that.) This permits a + more natural way to specify the link between GPSD + and NTPD: Simply name the device as it was given + to GPSD. +

Note: GPSD (as of version 3.10) cannot use kernel - mode PPS on devices that are hot-plugged. This would require to - attach the PPS line discipline to the character special file, - which is not possible when running with root privileges already - dropped. This is not likely to change in the future. + mode PPS on devices that are hot-plugged or activated on demand. + This is not likely to change in the future. Have a look + at GPSD's -n (nowait) option.

@@ -168,7 +175,7 @@ 120s. Then it reverts to STI-only operation until the PPS is stable again for 40s, when strict mode is engaged again. -

Important Notice: This is an expiremental +

Important Notice: This is an experimental feature!
Switching between strict and STI-only mode will cause changes in offset and jitter. Use this mode only if STI-only works fairly well with your setup, @@ -209,7 +216,7 @@ primary clock unit (u mod 128). A secondary unit processes only the PPS data from GPSD and needs the corresponding master unit to work1. Use - the 'noselect' keyword on the primary unit if you are not + the 'noselect' keyword on the primary unit if you are not interested in its data.

The secondary unit employs the usual precautions before feeding clock samples:

@@ -225,7 +232,7 @@ only be used if the GPS receiver can be trusted for the quality of its PPS signal2. The PPS flag gets cleared if no - PPS records can be aquired for some time. The unit also flushes + PPS records can be acquired for some time. The unit also flushes the sample buffer at this point to avoid the use of stale PPS data.

Attention: This unit uses its own PPS fudge value