CODEWITHSUNDEEP
erlangrebar
rkmax
rkmax

Reputation: 18135

Something missing in the erlang development workflow

I'm new with erlang and rebar

recently i've readed tutorials about rebar

but i feel something is missing, example after compile and generate i run my app with the followging command rel/${nodeid}/bin/${nodeid} console test code etc. but when i close the console always i need kill my self the epmd.exe (from process explorer).

There is some tutorials about more complete for work with rebar?

Upvotes: 2

Views: 783

Answers (2)

Paul Cager
Paul Cager

Reputation: 1920

Leaving epmd running permanently is usually no problem. What is happening here is that the workflow is continually creating epmd.exe, starting it and then trying to delete it - which won't work on Windows.

The easiest workaround I have found is to start epmd outside of your directory hierarchy, before you run rebar. E.g.

     "C:\Program Files\erl5.9.3.1\erts-5.9.3.1\bin\epmd"

If it is already running then the Erlang runtime won't try to start it from your release folder.

Upvotes: 2

Pascal
Pascal

Reputation: 14042

epmd is the erlang portmapper daemon. It is started automatically if it does not already exist, and the default behavior is to continue running, after any erlang VM stop.

I don't know any option to change this behavior, the command epmd -kill should kill the process as long as no more nodes are registered. you can check it with the command epmd -names

Upvotes: 5

Related Questions