bitwalker / exrm

Automatically generate a release for your Elixir project!

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Log messages have iex prefix on started release

liveforeverx opened this issue · comments

Probably I need to switch to other logging, but default logging to file by start writing this before every message, which is little bit annoying, but probably is idea, that it works in this way?

Every log message have:

iex(app@node)1>

By checking release script, I see: START_OPTION="console"

    start)
      shift
      START_OPTION="console"
      HEART_OPTION="start"
      ;;

Unfixed in 9184f2e

@hamiltop Attach does not work if the daemon is started with foreground, it has to be started with console unfortunately, so this is less of a regression, rather than a calculated tradeoff. If anyone has ideas on how to resolve both issues, I'm open, but attach is more important to me than removing the iex prompt from the log file.

Why is attach important? I can't think of a use case that remote_console
doesn't solve.

On Sun, Aug 7, 2016, 9:04 PM Paul Schoenfelder notifications@github.com
wrote:

@hamiltop https://github.com/hamiltop Attach does not work if the
daemon is started with foreground, it has to be started with console
unfortunately, so this is less of a regression, rather than a calculated
tradeoff. If anyone has ideas on how to resolve both issues, I'm open, but
attach is more important to me than removing the iex prompt from the log
file.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#361 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVqIEQjCedQl3B1P1v15GDU8YL-IHWZks5qdqrjgaJpZM4IqbMX
.

remote_console requires establishing a connection to the node, if for some reason the node is not responding to pings/remote connections, you can still get to a shell on the node with attach, because it just attaches the terminal to the pipe for the shell of the running node. In my opinion it's an important failsafe if you need to access a node to do troubleshooting in a situation like that. Obviously remote_console should be everyone's go-to for shelling into a node, but attach exists because it fills in a critical gap for introspection/surgery of a live system - if you can't remotely access the system, you'd be out of luck without attach.