package: use service_running instead of service_started for ubus config

Fixes issue with loading config after a service crash. Should also improve
startup time.

Signed-off-by: Felix Fietkau <[email protected]>

package/libs/udebug/files/udebug.init

@@ -49,7 +49,7 @@ service_triggers() {
 	procd_add_reload_trigger udebug
 }
 
-service_started() {
+service_running() {
 	ubus -t 10 wait_for udebug
 	[ $? = 0 ] && reload_service
 }

package/network/config/qosify/files/qosify.init

@@ -165,7 +165,7 @@ start_service() {
 	procd_close_instance
 }
 
-service_started() {
+service_running() {
 	ubus -t 10 wait_for qosify
 	[ $? = 0 ] && reload_service
 }

package/network/services/bridger/files/bridger.init

@@ -43,7 +43,7 @@ start_service() {
 	procd_close_instance
 }
 
-service_started() {
+service_running() {
 	ubus -t 10 wait_for bridger
 	[ $? = 0 ] && reload_service
 }

package/network/services/omcproxy/files/omcproxy.init

@@ -157,7 +157,7 @@ start_service() {
 	echo 128 > /proc/sys/net/ipv4/igmp_max_memberships
 }
 
-service_started() {
+service_running() {
 	procd_set_config_changed firewall
 }
 

package/network/services/umdns/files/umdns.init

@@ -66,7 +66,7 @@ start_service() {
 	procd_close_instance
 }
 
-service_started() {
+service_running() {
 	ubus -t 10 wait_for umdns
 	[ $? = 0 ] && reload_service
 }