erl_call -q

[Bogdan Andu]

But this defeats the purpose of NOT having a dedicated node to run a
dedicated module
to just stop nodes. Really? I was expecting this 'solution'.
C'mon man, this is erlang we are talking about!

It could do better than this!




On Tue, Mar 29, 2022 at 4:27 PM Luke Bakken <luke@REDACTED> wrote:

> At this point I would put together a small module, and use -s or -eval
> to run the code. erlc is right there!
>
> On Tue, Mar 29, 2022 at 6:26 AM Bogdan Andu <bog495@REDACTED> wrote:
> >
> > I know erl -eval, but elixir --rpc-eval gives the error also, like this:
> > --rpc-eval : RPC failed with reason :nodedown
> > while erl -eval is silent about errors like node down which is very
> important.
> >
> > May be a try catch would do the trick but already is too much to pass to
> eval.
> >
> > On Tue, Mar 29, 2022 at 3:57 PM Luke Bakken <luke@REDACTED> wrote:
> >>
> >> Give "-eval" a try instead.
> >>
> >> On Tue, Mar 29, 2022 at 5:40 AM Bogdan Andu <bog495@REDACTED> wrote:
> >> >
> >> > Hi,
> >> >
> >> > I tried that before like this:
> >> > $ erl -setcookie proxy -proto_dist inet_tls -ssl_dist_optfile
> file_with_pem -name 'stop-node@REDACTED' -s rpc call target-node@REDACTED init
> stop []
> >> > Erlang/OTP 24 [erts-12.3] [source] [64-bit] [smp:4:4] [ds:4:4:10]
> [async-threads:1]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20220329/912a77f7/attachment.htm>