From 1549d11da82a7f4ad6622414807466f5a8a008d6 Mon Sep 17 00:00:00 2001 From: "Gary E. Miller" Date: Fri, 8 Mar 2019 13:05:14 -0800 Subject: timeservice=yes: Fix the doc matches the code. The doc said timeservice=yes forced gpsd option -n, which it did not. That option also force building of ntpshmmon, cgps and gpsmon, even if disabled by gpsdclients=no. So it essentually did nothing when used per the clockmaker script. --- www/gpsd-time-service-howto.adoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'www') diff --git a/www/gpsd-time-service-howto.adoc b/www/gpsd-time-service-howto.adoc index d0bb61ef..325a545b 100644 --- a/www/gpsd-time-service-howto.adoc +++ b/www/gpsd-time-service-howto.adoc @@ -302,9 +302,11 @@ is mostly autoconfiguring and requires no special setup. You can build a version stripped to the mimimum configuration required for time service. This reduces the size of the binary and may be helpful on embedded systems or for SBCs like the Raspberry Pi, Odroid, -or BeagleBone. Also, when gpsd is built in this way, the -n (nowait) -option is forced; gpsd opens its command-line devices immediately on -startup. +or BeagleBone. Only do this if you have serious size contraints. When +gpsd is built in this way, the -n (nowait) option is forced: gpsd opens +its command-line devices immediately on startup. The timerservice=yes +option also forces the building of ntpshmmon, cgps and gpsmon. Those +program would be built by default anyway, unless gpsdclients=n0. Do it like this: -- cgit v1.2.1