DescriptionAs the Pi doesn't have an onboard clock, need a reliable method of ensuring that the system time is correct.
Whilst the Wifi connectivity could be used to establish a connection to a NTP server, the availability of a connection can't be guaranteed.
Given that the GPS unit knows the exact time, need to implement something that takes this timestamp and adjusts the system time as needed.
Will obviously need a config variable to define how regularly this check runs
Activity
2013-12-22 23:20:40
2013-12-22 23:20:42
2013-12-27 01:36:32
GPSD writes the NMEA time into a Shared Memory segment (SHM) owned by root. Unfortunately someone (at some point) decided that it'd be wise to run NTP as user ntp rather than as root. As a result, NTP can't actually access the SHM and so can't retrieve the current date. The change, helpfully, was buried in NTPs init script so may well need reverting again if NTP is ever updated
Will still need to adjust the offset, but the system should now get a accurate time/date pretty shortly after boot, even when no connectivity is present.
2013-12-27 01:36:38
2013-12-27 01:36:38
2013-12-27 01:36:44