gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] ntpshm_link_activate failing for pty source devices


From: David Thornley
Subject: Re: [gpsd-users] ntpshm_link_activate failing for pty source devices
Date: Thu, 17 Aug 2017 00:17:49 +0000
User-agent: Microsoft-MacOutlook/f.21.0.170409

Gary,

This is not urgent for me, I have patched in my own openwrt package build 
process, so not a biggie.

I think it would be better addressed at a later stage anyway given it is only 
affecting me, raising an issue sounds like it would suffice.

Regarding your suggestion, it doesn’t really apply in my case. We are using 
chrony which I’m pretty sure only uses the SHM or SOCK options for clock sync 
(the latter looks specifically developed for chrony). Both SHM+SOCK are broken 
in our case due to that condition. Also note that this is an embedded MIPS 
system so everything is self-contained, although we have a need to supply a 
couple of NMEA feeds to other hardware peripherals (hence kplex). We use gpsd 
and the built-in json protocol over TCP for our own in-house applications 
(which works great!)

Thanks again for your time! Being from Australia, I am envious of that eclipse 
frenzy (

Regards,

David.


On 17/8/17, 9:35 am, "gpsd-users on behalf of Gary E. Miller" <address@hidden 
on behalf of address@hidden> wrote:

    Yo David!
    
    On Wed, 16 Aug 2017 22:58:08 +0000
    David Thornley <address@hidden> wrote:
    
    > +//    if (session->sourcetype == source_pty)
    > +// return;
    > As you can see I just commented out the condition mentioned in my
    > original post. (
    
    Yeah.  We're gonna need to something better.  I'll create an issue for
    this now.  With the eclipse craziness it may take a bit to get fixed
    in git head.
    
    > I’m surprised others have not reported this before, the kplex (mux)
    > approach we use must be atypical…
    
    First I have heard of something like this. More typical is to run gpsd on
    the same host as the GPS and connect to it with gpsd protocol.  Then
    use ntpd to supply the time to the local network.  You'll get much better
    time that way.  Or have gpsd direclty connect to the remote GPS on udp.
    
    RGDS
    GARY
    ---------------------------------------------------------------------------
    Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588
    
            Veritas liberabit vos. -- Quid est veritas?
        "If you can’t measure it, you can’t improve it." - Lord Kelvin
    


reply via email to

[Prev in Thread] Current Thread [Next in Thread]