From 115b4683cc6092b8f11bcadc4906b82de4aa39d4 Mon Sep 17 00:00:00 2001 From: Mukund Sivaraman Date: Fri, 19 Oct 2018 17:01:21 -0700 Subject: Minor typo in the time service howto. Signed-off-by: Gary E. Miller --- www/gpsd-time-service-howto.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'www') 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. -- cgit v1.2.1