[erlang-questions] Including erl_call in the release tarball

Michał Ptaszek erlang@REDACTED
Thu Jan 3 19:23:39 CET 2013


I'm running my system in the embedded mode, and trying to apply live
upgrades using release_handler. Nonetheless, in order to automate the
process, I would like to interface with the running Erlang node via
'erl_call' command and pass the release_handler instructions as arguments
(I would love to avoid writing escripts or playing with 'erl -eval
"rpc:call(...)"' mumbo-jumbo).

Unfortunately, it seems like erl_call is not included in the release
package generated by rebar, and to make things worse - is not even put in
the standard erlang bin/ directory. Instead, by default, it's located under

Also, trying to add erl_interface application to the released apps does not
work, as erl_interface is not an OTP application (does not have .app file).

What would be the best way to make sure that the target release package
contains erl_call binary? How do you usually make it accessible/available
on the target system?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130103/9f1a5fae/attachment.htm>

More information about the erlang-questions mailing list