- mlat-client: always use beast connect to send data to mlathub: this
eliminates mlathub 'connection failed' messages on container startup
- remove unused infrastructure around /run/mlathub_up
When no adsbexchange uuid was present the sed replacement can fail to
replace anything because the pattern doesn't exist.
In that case the entire readsb conf array is used as an UUID.
Fix that by checking each conf array entry if there is a adsbexchange
uuid and only then use the sed replace.
Move file cleanups into a finish script for the service that created the
file (replace 02 / replace 03 commits)
Currently there is a whole dependency forest just to start a couple of
startup scripts in order.
Additionally all the services also have a dependency on all the startup
scripts.
This is unnecessary complex, simplify it:
- Move startup scripts to /etc/s6-overlay/startup.d
- oneshot service named "startup" from underlying image executes
all files in /etc/s6-overlay/startup.d in alphabetical order
- Remove various oneshot scripts from longrun service dependencies
Add "startup" oneshot service to longrun service dependencies
container-version is now being run by said startup script, remove the
double s6wrap prepending of an appropriate log name.
Move startup scripts to /etc/s6-overlay/startup.d
oneshot service named "startup" from underlying image executes
all files in /etc/s6-overlay/startup.d in alphabetical order
Remove various oneshot scripts from longrun service dependencies
Add "startup" oneshot service to longrun service dependencies
03-remove-mlathub-up deletes /run/mlathub_up when the container stops
As this file is created by the mlat-client service, remove it instead in
a finish script for mlat-client which is run when the mlat-client
service is stopped
02-remove-prometheus-data deletes /run/readsb-prometheus.prom when
the container stops
As this file is created by readsb, remove it instead in a finish script
for readsb which is run when the readsb service is stopped
