It’s antiX not Anti-X. The antiX delevoper’s attitude about systemd is “never had it, never will.” Rather than trying to change either the distro or dump1090-fa, just use a different distro. There are hundreds to choose from.
Developers of Linux distros make certain decisions about what to include and what to omit. In this case the dev chose to use a different init system. I think it’s SysV init but 'm not 100% sure.
Apparently dump1090-fa comes with only a systemd service script file. You would have to write an init.d sript for dump1090-fa, or ask the FlightAware devs to include one with the app so it can work with either init system.
The contents of the init file /etc/init.d/dump1090-fa.sh are as follows:
#!/bin/bash
### BEGIN INIT INFO
#
# Provides: dump1090-fa
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: dump1090-fa initscript
#
### END INIT INFO
## Fill in name of program here.
PROG="dump1090-fa"
PROG_PATH="/usr/share/dump1090-fa/start-dump1090-fa"
PIDFILE="/var/run/dump1090-fa.pid"
start() {
if [ -e $PIDFILE ]; then
## Program is running, exit with error.
echo "Error! $PROG is currently running!" 1>&2
exit 1
else
## Change from /dev/null to something like /var/log/$PROG if you want to save output.
cd $PROG_PATH
./$PROG $PROG_ARGS 2>&1 >/dev/null &
echo "$PROG started"
touch $PIDFILE
fi
}
stop() {
if [ -e $PIDFILE ]; then
## Program is running, so stop it
echo "$PROG is running"
killall $PROG
rm -f $PIDFILE
echo "$PROG stopped"
else
## Program is not running, exit with error.
echo "Error! $PROG not started!" 1>&2
exit 1
fi
}
## Check to see if we are running as root first.
## Found at http://www.cyberciti.biz/tips/shell-root-user-check-script.html
if [ "$(id -u)" != "0" ]; then
echo "This script must be run as root" 1>&2
exit 1
fi
case "$1" in
start)
start
exit 0
;;
stop)
stop
exit 0
;;
reload|restart|force-reload)
stop
start
exit 0
;;
**)
echo "Usage: $0 {start|stop|reload}" 1>&2
exit 1
;;
esac
exit 0
The error message shown inside red rectangle in screenshot of PuTTY below keeps on recurring.
Not sure, but seems this is reason for a blank map and blank aircraft table in skyaware map.
Clarification: MX Linux includes systemd and makes it available in its GRUB boot menu for those who prefer it or use apps that require it, it just defaults to SysV init. It’s been my daily driver OS for going on 4 years.
I have no idea why but some people object to systemd for whatever reason. Me, I just want my computer to boot up, run, and let me do what I want to do I don’t care what init system it uses.
It’s unusual to have a debian-like system that does not have systemd, and that’s the only packaging we support, so supporting sysvinit scripts has not been a high priority.
That said I don’t have any objections to a PR to add a sysvinit script, if it is equivalent to what the systemd service does (i.e. accepts the same config etc) and plays nicely with regular Debian.
