root@odroid:~# systemctl status airspy_adsb
● airspy_adsb.service - Airspy ADS-B receiver
Loaded: loaded (/etc/systemd/system/airspy_adsb.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-04-11 13:54:21 UTC; 3min 25s ago
Docs: HOWTO: Airspy mini and Airspy R2: Piaware / dump1090-fa configuration - #2 by wiedehopf
Main PID: 2071 (airspy_adsb)
CGroup: /system.slice/airspy_adsb.service
└─2071 /usr/local/bin/airspy_adsb -v -f 1 -b -l 29999:beast -l 47806:asavr -c localhost:30104:beast -g 19 -m 20Apr 11 13:54:21 odroid systemd[1]: Started Airspy ADS-B receiver.
Apr 11 13:54:21 odroid airspy_adsb[2071]: Listening for beast clients on port 29999
Apr 11 13:54:21 odroid airspy_adsb[2071]: Listening for asavr clients on port 47806
Apr 11 13:54:21 odroid airspy_adsb[2071]: Acquired Airspy device with serial XXXXXXXX
Apr 11 13:54:21 odroid airspy_adsb[2071]: Decoding started at 20 MSPS
Apr 11 13:54:33 odroid airspy_adsb[2071]: Push client connected to localhost:30104 (beast)
root@odroid:~#
Sure enough, MyADS-B page claims it is connected and feeding, including MLAT.
In the next few days (barring business travel) I will start with a fresh sd-card from scratch. That can see if ln -s arm-linux-gnueabihf/ld-2.23.so ld-linux.so.3 is necessary. it is included today.