diff options
| author | Mukund Sivaraman <muks@isc.org> | 2018-10-19 17:01:21 -0700 |
|---|---|---|
| committer | Gary E. Miller <gem@rellim.com> | 2018-10-19 17:01:21 -0700 |
| commit | 115b4683cc6092b8f11bcadc4906b82de4aa39d4 (patch) | |
| tree | ef780fa70c37b2859993912ad4994aed05fddc5d /www | |
| parent | 68f465d82816e10690f2f32fae891811b621d53b (diff) | |
| download | gpsd-115b4683cc6092b8f11bcadc4906b82de4aa39d4.tar.gz | |
Minor typo in the time service howto.
Signed-off-by: Gary E. Miller <gem@rellim.com>
Diffstat (limited to 'www')
| -rw-r--r-- | www/gpsd-time-service-howto.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/www/gpsd-time-service-howto.txt b/www/gpsd-time-service-howto.txt index a643e443..a3204d65 100644 --- a/www/gpsd-time-service-howto.txt +++ b/www/gpsd-time-service-howto.txt @@ -1098,7 +1098,7 @@ throw off the time measurements to servers on the local lan. On a RaspberryPi ARP has been shown to impact the remote offset by up to 600 uSec in some rare cases. -The solution is the same for both ntpd and chronyd, add the "minpoll 5" +The solution is the same for both ntpd and chronyd, add the "maxpoll 5" command to any 'server" or "peer directive. This will cause the maximum polling period to be 32 seconds, well under the 60 second ARP timeout. |