From 03e0c5ef2a53ee90020155354a1949f44ca5cc82 Mon Sep 17 00:00:00 2001
From: Thales Macedo Garitezi <thalesmg@gmail.com>
Date: Thu, 6 Jan 2022 17:24:47 -0300
Subject: [PATCH] fix(eval): use running node for rpc eval, not a fresh one

With the previous arguments, a fresh hidden node with the same name as
the expected running one was being started and commands were being run
there.  This caused commands like `ekka_cluster:info()` to report
seemingly weird results.
---
 bin/emqx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/bin/emqx b/bin/emqx
index 8bd3640fa..2e1803eff 100755
--- a/bin/emqx
+++ b/bin/emqx
@@ -864,10 +864,12 @@ case "${COMMAND}" in
         then
           "$REL_DIR/elixir" \
               --hidden \
+              --name "rand-$(relx_gen_id)-$NAME" \
               --cookie "$COOKIE" \
               --boot "$REL_DIR/start_clean" \
               --boot-var RELEASE_LIB "$ERTS_LIB_DIR" \
-              --vm-args "$(latest_vm_args 'EMQX_NODE__NAME')"\
+              --vm-args "$REL_DIR/remote.vm.args" \
+              --erl "-start_epmd false -epmd_module ekka_epmd" \
               --rpc-eval "$NAME" "$@"
         else
           relx_nodetool "eval" "$@"