Uploaded image for project: 'Erlang/OTP'
  1. Erlang/OTP
  2. ERL-1463

erl_call output to stdout

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Backstory: relx moved to using `erl_call` for rpc/eval commands to a running node from its own escript, `nodetool`. This has led to an issue for users who expect output to be printed to their stdout and an env variable `USE_NODETOOL` has had to be added to allow users to force use of `nodetool` (meaning we have to keep maintaining and always including it in releases).

       

      Lukas' comment on resolving this in `erl_call` was:

       

      There is no way right now to get that. We would have to implement an IO server in erl_call or add a proxy on the erlang side that takes care of it.

      https://erlang.org/doc/apps/stdlib/io_protocol.html

      It is not very complicated to do, but not simple either...

      Opening this ticket to track the issue.

        Attachments

          Activity

            People

            Assignee:
            otp_team_vm Team VM
            Reporter:
            tsloughter tsloughter
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: