Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We run erlang in production and have noticed that it is quite easy to shoot yourself in the foot when accidentally typing ctrl-c or ctrl-s. Both of these shortcuts are easy to type if you are reaching for ctrl-a, ctrl-d or ctrl-r. ctrl-c by default will run the erlang emulator break handler that will pause the node. This can be destructive on a live system. ctrl-s will cause erlang to block flow control which has some very undesirable effects (see here: http://erlang.org/pipermail/erlang-patches/2010-March/000883.html)
The option to disable the break handler is commented out the vm_args file but you might want to make it the default.
I've also included a change to the script that will set the TERM variable to something sane. For example when deploying from capistrano this will be set to 'dumb' I think which causes problems when you attach to the node. However, it might be better to just hardcode TERM to a particular value. I'm not sure.