You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ive used rtl-tcp for a long time in the command. I dont like tending the rtl-tcp in command-line on each RPI I run it on. I recently set dump 1090 to run as a int.d script, it keeps it going when im not around. So I thought ... why can I do this with the rtl-tcp. I use sdr#, GHPSDR3, GRC to connect to RPI nodes in remote locations, rtl-tcp dosnt always exit cleanly it gets worse with a -4 and that requires a REBOOT. I dont see, that the LibSDR programs are written to report different exit variables in a manner that I can write case for an int.d script. Im trying to keep rtl-tcp running. Some crashes are complicated like -4 with the kernel module fail, I can just rerunning the command.
Any Ideas or help to stream line the programs for a int.d scripts.
73 Mathison kj6dzb
The text was updated successfully, but these errors were encountered:
Ive used rtl-tcp for a long time in the command. I dont like tending the rtl-tcp in command-line on each RPI I run it on. I recently set dump 1090 to run as a int.d script, it keeps it going when im not around. So I thought ... why can I do this with the rtl-tcp. I use sdr#, GHPSDR3, GRC to connect to RPI nodes in remote locations, rtl-tcp dosnt always exit cleanly it gets worse with a -4 and that requires a REBOOT. I dont see, that the LibSDR programs are written to report different exit variables in a manner that I can write case for an int.d script. Im trying to keep rtl-tcp running. Some crashes are complicated like -4 with the kernel module fail, I can just rerunning the command.
Any Ideas or help to stream line the programs for a int.d scripts.
73 Mathison kj6dzb
The text was updated successfully, but these errors were encountered: