[PATCH] hostapd: pass respawn settings when registering the service

John Crispin john at phrozen.org
Fri Dec 11 02:07:40 EST 2020


When hostapd gets restarted to often/quickly will cause procd to not restart it
anymore. it will think that hapd is in a crash loop.

Signed-off-by: John Crispin <john at phrozen.org>
---
 package/network/services/hostapd/files/wpad.init | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/network/services/hostapd/files/wpad.init b/package/network/services/hostapd/files/wpad.init
index 3198e9801f..e2cd380cb5 100644
--- a/package/network/services/hostapd/files/wpad.init
+++ b/package/network/services/hostapd/files/wpad.init
@@ -11,7 +11,7 @@ start_service() {
 		mkdir -p /var/run/hostapd
 		procd_open_instance hostapd
 		procd_set_param command /usr/sbin/hostapd -s -g /var/run/hostapd/global
-		procd_set_param respawn
+		procd_set_param respawn 3600 5 0
 		procd_close_instance
 	fi
 
@@ -19,7 +19,7 @@ start_service() {
 		mkdir -p /var/run/wpa_supplicant
 		procd_open_instance supplicant
 		procd_set_param command /usr/sbin/wpa_supplicant -n -s -g /var/run/wpa_supplicant/global
-		procd_set_param respawn
+		procd_set_param respawn 3600 5 0
 		procd_close_instance
 	fi
 }
-- 
2.25.1




More information about the openwrt-devel mailing list