Re: [gpsd-users] time setting chicken and egg

> What I've done in the past is to just directly read the GPS NMEA
> stream, parse out the time, set the date/time, and then fire up gpsd
> and let it handle fine adjustments.
>
> On Sun, Oct 23, 2011 at 9:50 PM, Yan Seiner <yan@...
> <mailto:yan@...>> wrote:
>
>     I'm working on a platform that is mobile it sometimes has access
>     to the internet and sometimes not.   The hardware does not have a
>     RTC so at power-up it sets the clock to something like Dec 31, 1969.
>
>     I'm trying to set up chrony + gpsd to set the time from the gps
>     directly.
>
>     The behavior I'm seeing from gpsd is that it won't report a time
>     to chrony until the system clock is close to what gpsd is seeing
>     from the gps.  I have not found a way to override this.
>
>     I'm attaching a log of what happens.  On wifi connect the system
>     gets a system time via rdate, at which point gpsd and chrony start
>     to function normally.  You can see that gpsd reports a discrepancy
>     and chrony doesn't set the clock at all.....
>
>     Does anyone have any ideas on where to look?
>
>     --
>     Few people are capable of expressing with equanimity opinions
>     which differ from the prejudices of their social environment. Most
>     people are even incapable of forming such opinions.
>       Albert Einstein
>