strongswan: use procd running check

Instead of using the standard procd check, the function is overridden, and
the check to see if the service is running is performed using the command
'swanctl --stats > /dev/null 2>&1'. The problem with this is, that this
call is blocking if the strongswan charon socket is not available. The call
does not  return until the timeout has expired.

This block does not occur if we use the standard behavior of procd, which
checks whether the service it started is actually running. This change
therefore uses the standard call via procd, which returns the value without
blocking.

Signed-off-by: Florian Eckert <redacted>

diff --git a/net/strongswan/files/swanctl.init b/net/strongswan/files/swanctl.init
index 6826331dbacd2be817c92ffe7f55a5fb7b837996..59090490d788363e3803c38ef650c39212e8ca40 100644 (file)
--- a/net/strongswan/files/swanctl.init
+++ b/net/strongswan/files/swanctl.init
@@ -739,10 +739,6 @@ prepare_env() {
        do_postamble
 }
 
-service_running() {
-       swanctl --stats > /dev/null 2>&1
-}
-
 reload_service() {
        running && {
                prepare_env