gpsd-users
[Top][All Lists]
Advanced

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

Re: NTP via tcp NMEA feed


From: Nick Taylor
Subject: Re: NTP via tcp NMEA feed
Date: Fri, 14 Oct 2022 22:01:11 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0

Yo Gary

I was hoping that NMEA contained enough time info that the dest gpsd
could still obtain time and broadcast on the shm segment as readable
with ntpshmmon.
Which is eacatly what it does.
Sorry to be a pain, but I'm still not quite clear... If you refer back to my original post I show the output from gpspipe which contains time, but ntpshmmon shows no output.

If you are saying that gpsd fed via tcp NMEA stream should still be outputting to the shm then that doesn't seem to be working for me...

We have fallback time sources via htpdate or using last resort of
picking up time from our https servers and using that.
If you have even intermittent internet, then use NTP protocol.
Agreed - however sadly we have no access to NTP at several of our sites that are tightly firewalled and connected only via proxy server
As I say accuracy not important here but I'm kind of coming to
understand that my expectation of time just appearing into dest gpsd
feed via NMEA and appearing in shm is not going to happen!!
gpsd has worked that way for a long time.  So nothing needs to happen
in gpsd.
gpsd is picking up time and this is visible fine using cgps, but there's no shm feed visible using ntpshmmon

If this is expected behaviour then fine - but if there should be ntp feed appearing in shm then that's not what I'm seeing...

Apologies if this has got a little confused...

Best regards

Nick



reply via email to

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