Unbound Wrong installation path

[rlj2]

Unbound install through amtm sets the path in service-event to /jffs/scripts/unbound_stats.sh , the correct path is /jffs/addons/unbound/unbound_stats.sh .
Noticed this through many resets.

 

[Martineau]

Unbound install through amtm sets the path in service-event to /jffs/scripts/unbound_stats.sh , the correct path is /jffs/addons/unbound/unbound_stats.sh .
Noticed this through many resets.

Are you on the latest version.....what does the following show?

find /jffs/ -name "unbound_stats.sh" -type f -exec grep -F 'SCRIPT_VERSION=' {} +

 

[rlj2]

Are you on the latest version.....what does the following show?

find /jffs/ -name "unbound_stats.sh" -type f -exec grep -F 'SCRIPT_VERSION=' {} +

readonly SCRIPT_VERSION="v1.3.0" << shows this from your command.
shows in amtm

7 open unbound Manager v3.21
Installing through amtm. Ive done a crapload of different firmwares, factory resets lately. Ive had to change path everytime.
Heres another version it shows.
unbound (pid 3437) is running... uptime: 0 Days, 04:30:59 version: 1.12.0 # Version=v1.11 Martineau update (Date Loaded by unbound_manager Sat Jan 16 05:45:57 EST 2021)

 

[Martineau]

readonly SCRIPT_VERSION="v1.3.0" << shows this from your command.
shows in amtm

7 open unbound Manager v3.21
Installing through amtm. Ive done a crapload of different firmwares, factory resets lately. Ive had to change path everytime.

The entry in service-event is managed by unbound_stats.sh and its install path variable should be revealed by

find /jffs/ -name "unbound_stats.sh" -type f -exec grep -E 'SCRIPT_VERSION=|SCRIPT_DIR=' {} +

You could manually remove unbound_stats.sh from service-event and trace the sh -x /jffs/addons/unbound/unbound_stats.sh install command

 

[rlj2]

The entry in service-event is managed by unbound_stats.sh and its install path variable should be revealed by

find /jffs/ -name "unbound_stats.sh" -type f -exec grep -E 'SCRIPT_VERSION=|SCRIPT_DIR=' {} +

You could manually remove unbound_stats.sh from service-event and trace the sh -x /jffs/addons/unbound/unbound_stats.sh install command

Under Autoservice in your script, it only puts the correct path IF service-event is already present. On a new install it is not.
service-event after running unbound_stats.sh install twice

#!/bin/sh

/jffs/scripts/unbound_stats.sh generate "$1" "$2" & # Unbound_Stats.sh
/jffs/addons/unbound/unbound_stats.sh generate "$1" "$2" & # Unbound_Stats.sh

 

[Martineau]

Under Autoservice in your script, it only puts the correct path IF service-event is already present. On a new install it is not.
service-event after running unbound_stats.sh install twice

#!/bin/sh

/jffs/scripts/unbound_stats.sh generate "$1" "$2" & # Unbound_Stats.sh
/jffs/addons/unbound/unbound_stats.sh generate "$1" "$2" & # Unbound_Stats.sh

FYI unbound_stats.sh is not my script....my unbound_manager.sh script simply downloads it from @juched's Github.

https://github.com/MartineauUK/Unbound-Asuswrt-Merlin/blob/master/unbound_manager.sh#L2575