First install of this version, some annoying problems.
Maybe something for Khan to have a look at.
1. It drops a lot of unused crap in the directories. I do NOT want to have service files and log files for parts that are not used.
If we don't enable UAT, the / etc / systemd / system / fr24uat-feed.service should be deleted or never created. It also screws up tab-completion when using systemctl commands.
It creates / var / log / fr24feed_install_dump1090.log , even if dump is not used, installed, or asked for.
It tries to run / usr / lib / fr24 / create_missing_directories.sh, but that fails, unclear why. /var and /run are RAM-disks, but we have been using the same setup since 2015 and never had problems with this before.
2. It no longer creates a logfile at / var / log / fr24feed
The entries
logmode= 1
logpath= / var / log / fr24feed
are no longer inserted into / etc / fr24feed.ini as default. But I think this happened some versions ago?
Is the log file at another location? Or missing, related to problem above?
The paths are correct, but some annoying anti-exploit filter is preventing the posting of proper / paths...
BR
/ M
Maybe something for Khan to have a look at.
1. It drops a lot of unused crap in the directories. I do NOT want to have service files and log files for parts that are not used.
If we don't enable UAT, the / etc / systemd / system / fr24uat-feed.service should be deleted or never created. It also screws up tab-completion when using systemctl commands.
It creates / var / log / fr24feed_install_dump1090.log , even if dump is not used, installed, or asked for.
It tries to run / usr / lib / fr24 / create_missing_directories.sh, but that fails, unclear why. /var and /run are RAM-disks, but we have been using the same setup since 2015 and never had problems with this before.
2. It no longer creates a logfile at / var / log / fr24feed
The entries
logmode= 1
logpath= / var / log / fr24feed
are no longer inserted into / etc / fr24feed.ini as default. But I think this happened some versions ago?
Is the log file at another location? Or missing, related to problem above?
The paths are correct, but some annoying anti-exploit filter is preventing the posting of proper / paths...
BR
/ M
Comment