|
From: | Nick Taylor |
Subject: | Re: gpsd Reliable and resilient tcp feed |
Date: | Thu, 30 Sep 2021 12:45:02 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 |
Hi all We are really struggling with this...We need to use tcp feed into gpsd - our customer is providing the feed so udp not really an option.
Requirement is for reliable and resilient tcp feed to gpsd. Currently it doesn't do very well if feed gets interrupted - either by restart of the feed or if we block the connection for a while with iptables to simulate interrupted feed.
I realise that gpsd is a complex beast and our guy hasn't yet come up with working solution - we keep getting bad side effects like gpsd failing to respond to client connects and broken shm ntp feed
Any gpsd gurus here interested in some contract work - or can anyone point us to someone who could help??
Many thanks Nick On 24/09/2021 22:16, Gary E. Miller wrote:
Yo Nick! On Fri, 24 Sep 2021 15:57:30 +0100 Nick Taylor <nicktaylor@dataskill.uk> wrote:We would appreciate some help... It seems that the option for using NMEA tcp feed to gpsd isn't very tolerant to network feed disconnects...Why not UDP?Attached please find our patch as it is so far, together with debug log showing where the tcp connect hangs...You already sent that patch. Same issues I found then are still there. RGDS GARY --------------------------------------------------------------------------- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 gem@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can't measure it, you can't improve it." - Lord Kelvin
[Prev in Thread] | Current Thread | [Next in Thread] |