Re: gpsd tcp NMEA feed

[Nick Taylor]

Yo Gary

Thanks for looking at this...

On 01/10/2022 03:33, Gary E. Miller wrote:
> > > Feed can be seen on machine B using telnet, but it seems gpsd
> > > doesn't notice the failed connection and the only way I found to
> > > recover is to restart gpsd
> > Looks to me like it sees the failed connection, otherwise why would
> > it try to awaken the device again?
> I have not had time to duplicate the problem, but I did push a change
> that sets SO_KEEPALIVE on  tcp:// connections.  Dunno if that helps
> or not, but easy to do and can't hurt anything.
Sadly doesn't appear to have made any difference:

root@TSB-318:~# gpsd -V
gpsd: 3.24.1~dev (revision release-3.24-274-g1df61193e)
root@TSB-318:~#

gpsd:PROG: CORE: pselect: timeout
gpsd:PROG: checking client(0)
gpsd:CLIENT: <= client(0): ?WATCH={"enable":true,"json":true};

gpsd:PROG: awaken(0) fd 7, path tcp://192.168.2.53:2948
gpsd:PROG: device 0 (fd=7, path tcp://192.168.2.53:2948) already active.
gpsd:CLIENT: => client(0) len 278: 
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"tcp://192.168.2.53
:2948","driver":"NMEA0183","activated":"2022-10-03T08:28:43.368Z","flags":1}]} 

{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false
,"pps":false}

gpsd:PROG: CORE: pselect: timeout
gpsd:PROG: gpsd_multipoll(7) DEVICE_UNCHANGED for 5
gpsd:PROG: checking client(0)
gpsd:CLIENT: <= client(0): ?WATCH={"enable":true,"json":true};

gpsd:PROG: awaken(0) fd 7, path tcp://192.168.2.53:2948
gpsd:PROG: device 0 (fd=7, path tcp://192.168.2.53:2948) already active.
gpsd:CLIENT: => client(0) len 278: 
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"tcp://192.168.2.53
:2948","driver":"NMEA0183","activated":"2022-10-03T08:28:43.368Z","flags":1}]} 

{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false
,"pps":false}
> I'll look at this in the coming week.
Fingers crossed :D

Thanks again

Nick