Fix stop-edge.sh failing to stop its own process when IOTDB_HOME is set

start-edge.sh honours an IOTDB_HOME from the environment and passes that value
to the JVM as -DIOTDB_HOME=..., while stop-edge.sh recomputed IOTDB_HOME from
its own location and matched the command line against that string. When the two
differ -- for example a versioned install reached through a symlink -- the stop
declined to act on its own process, exited 0 and removed the PID file, so a
service manager saw a successful stop while the process kept running.

stop-edge.sh now honours IOTDB_HOME the same way start-edge.sh does, and falls
back to comparing resolved paths when the literal match does not hit. The
original literal comparison is tried first, so any command line that matched
before still matches.

Author: PDGGK

scripts/sbin/stop-edge.sh

@@ -20,7 +20,17 @@
 
 # Stop IoTDB Edge (the merged ConfigNode + DataNode process).
 
-IOTDB_HOME="$(cd "$(dirname "$0")"/.. && pwd)"
+if [ -z "${IOTDB_HOME}" ]; then
+    IOTDB_HOME="$(cd "$(dirname "$0")"/.. && pwd)"
+fi
+
+# Resolve symlinks and relative segments so that the same installation reached
+# through a different path still compares equal.
+resolve_home() {
+    (cd "$1" 2>/dev/null && pwd -P) || printf '%s' "$1"
+}
+
+IOTDB_HOME_RESOLVED="$(resolve_home "${IOTDB_HOME}")"
 
 PID_FILE="${IOTDB_HOME}/edge.pid"
 
@@ -31,9 +41,14 @@ is_same_edge_home() {
             return 0
             ;;
         *)
-            return 1
             ;;
     esac
+    # Fall back to comparing resolved paths, so that a start-edge.sh invoked with
+    # IOTDB_HOME pointing at a symlink is still recognised here.
+    local home="${command_line#*-DIOTDB_HOME=}"
+    home="${home%% -D*}"
+    [ -n "$home" ] && [ "$home" != "$command_line" ] || return 1
+    [ "$(resolve_home "$home")" = "${IOTDB_HOME_RESOLVED}" ]
 }
 
 is_edge_process() {