On Wed, Nov 29, 2017 at 05:11:06PM -0500, Joe Smith wrote:
> I fiddled around with chronyd.service gpsd.service and I think I have
> something that works. Both gpsd and chronyd start successfully on boot.
Great.
> ** chronyd.service **
>
> [Unit]
> Description=chrony, an NTP client/server
>
Oops. Didn't see your other response. Yes, that "After" directive is mainly
what did the trick. I also removed "After=chronyd.service" from
gpsd.service as it seemed to be causing problems with gpsd startup.
Thanks for the links! I'll take a look at those to see if that's a better
way to have
Got rid of commandkey. I had planned to do that for a while but hadn't
because it didn't seem to be causing any serious problem.
That was precisely it. /dev/pps0 wasn't getting created by the kernel until
later in the bootup process. I had to make some changes to chronyd.service
and gpsd.service
On Wed, Nov 29, 2017 at 07:12:01AM -0800, Bill Unruh wrote:
> On Wed, 29 Nov 2017, Assaf Vainsencher wrote:
>
> > I'm not really sure but I think as long as chrony syncs with the NTP server
> > that it's acceptable for our needs. That being said, could it be that
> > both the NTP server
