From d00131e2a0c8e846b42df22eda6c8356d4fce4a9 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Hi=E1=BA=BFu=20L=C3=AA?= Date: Fri, 29 Sep 2023 19:45:14 +0000 Subject: [PATCH] adguardhome: wait for interfaces to be up at boot MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit This should allow the service to be activated even earlier during the boot process and also avoids race condition against network. Signed-off-by: Hiếu Lê --- net/adguardhome/files/adguardhome.init | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/net/adguardhome/files/adguardhome.init b/net/adguardhome/files/adguardhome.init index 802dcdae3a..6a29c4e4a3 100644 --- a/net/adguardhome/files/adguardhome.init +++ b/net/adguardhome/files/adguardhome.init @@ -4,12 +4,22 @@ PROG=/usr/bin/AdGuardHome USE_PROCD=1 -# starts just after network starts to avoid some network race conditions -START=25 +# matches dnsmasq +START=19 # stops before networking stops STOP=89 +boot() { + adguardhome_boot=1 + start "$@" +} + start_service() { + if [ -n "$adguardhome_boot" ]; then + # Do not start yet, wait for triggers + return 0 + fi + config_load adguardhome config_get WORK_DIR config workdir @@ -21,3 +31,11 @@ start_service() { procd_set_param stderr 1 procd_close_instance } + +service_triggers() { + if [ -n "$adguardhome_boot" ]; then + # Wait for interfaces to be up before starting AdGuard Home for real. + # Prevents issues like https://github.com/openwrt/packages/issues/21868. + procd_add_raw_trigger "interface.*.up" 5000 /etc/init.d/adguardhome restart + fi +} -- 2.30.2