For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the system change.

−

=== Start erlang as a node on your host===

+

=== Start an erlang node on your neo===

This is my /etc/X11/Xsession.d/80zhone. As you can see the erlang node's got a name "-name neo@192.168.0.202" (a running erlang virtual machine is called an erlang node). And it's got a cookie "-setcookie SFEWRG34AFDSGAFG35235". This is all that's needed on the neo.

This is my /etc/X11/Xsession.d/80zhone. As you can see the erlang node's got a name "-name neo@192.168.0.202" (a running erlang virtual machine is called an erlang node). And it's got a cookie "-setcookie SFEWRG34AFDSGAFG35235". This is all that's needed on the neo.

Line 12:

Line 13:

</pre>

</pre>

−

+

=== Start an erlang node on your host===

Every erlang node in your network should have a unique name, and a common cookie. Start an erlang node on your host PC with a unique name and the common cookie:

Every erlang node in your network should have a unique name, and a common cookie. Start an erlang node on your host PC with a unique name and the common cookie:

<pre>

<pre>

Line 18:

Line 19:

</pre>

</pre>

−

From your host erlang console try

+

Once again - first make sure you can access your neo from the host with ping, ssh ,rcp etc. Then, from your host erlang console try

Make sure erlang can find the compiled module 'your_modulename' on the local file system.

+

+

To carry out Hot Code Loading type (on your host erlang console):

<pre>

<pre>

net_adm:ping('neo@192.168.0.202').

net_adm:ping('neo@192.168.0.202').

nl(your_modulename).

nl(your_modulename).

</pre>

</pre>

+

nl() is short for network_load and will remotely load a compiled erlang module on every connected node on your network.

+

Substitute your_modulename with the name of the module you want to load into the virtual machine on your neo. The response should be 'abcast' if sucessful. If not the response is 'error'.

Substitute your_modulename with the name of the module you want to load into the virtual machine on your neo. The response should be 'abcast' if sucessful. If not the response is 'error'.

−

The ping command is only necessary the first time to let your host node find your neo node. When you are finished, don't forget to copy the compiled erlang file to your neo, hot code loading does not copy your beam file to the file system.

+

The ping command is only necessary the first time to let your host node find your neo node. When you are finished, don't forget to copy the compiled erlang file to your neo, hot code loading does not copy your beam file to the remote file system.

−

===Example Code===

+

==Example Code==

−

There is only one thing you must know when using hot code loading, and that is what makes your code reload. Every time the erlang VM finds a module_name:function_name() in your code it looks for (and uses) the most recent version it has loaded. So - just export your loop function and preface it with the module name:

+

There is only one thing you must know when using hot code loading, and that is what makes your code reload. Every time the erlang VM finds a module_name:function_name() in your code it looks for (and uses) the most recent version it has loaded. So - just export your loop function and preface it in your calls with the module name or with the macro ?MODULE:

This is my /etc/X11/Xsession.d/80zhone. As you can see the erlang node's got a name "-name neo@192.168.0.202" (a running erlang virtual machine is called an erlang node). And it's got a cookie "-setcookie SFEWRG34AFDSGAFG35235". This is all that's needed on the neo.

Make sure erlang can find the compiled module 'your_modulename' on the local file system.

To carry out Hot Code Loading type (on your host erlang console):

net_adm:ping('neo@192.168.0.202').
nl(your_modulename).

nl() is short for network_load and will remotely load a compiled erlang module on every connected node on your network.

Substitute your_modulename with the name of the module you want to load into the virtual machine on your neo. The response should be 'abcast' if sucessful. If not the response is 'error'.

The ping command is only necessary the first time to let your host node find your neo node. When you are finished, don't forget to copy the compiled erlang file to your neo, hot code loading does not copy your beam file to the remote file system.

There is only one thing you must know when using hot code loading, and that is what makes your code reload. Every time the erlang VM finds a module_name:function_name() in your code it looks for (and uses) the most recent version it has loaded. So - just export your loop function and preface it in your calls with the module name or with the macro ?MODULE:

Views

Personal tools

To change a running erlang system

Start erlang as a node on your host

This is my /etc/X11/Xsession.d/80zhone. As you can see the erlang node's got a name "-name neo@192.168.0.202" (a running erlang virtual machine is called an erlang node). And it's got a cookie "-setcookie SFEWRG34AFDSGAFG35235". This is all that's needed on the neo.

HotLoad the code

Substitute your_modulename with the name of the module you want to load into the virtual machine on your neo. The response should be 'abcast' if sucessful. If not the response is 'error'.

The ping command is only necessary the first time to let your host node find your neo node. When you are finished, don't forget to copy the compiled erlang file to your neo, hot code loading does not copy your beam file to the file system.

Example Code

There is only one thing you must know when using hot code loading, and that is what makes your code reload. Every time the erlang VM finds a module_name:function_name() in your code it looks for (and uses) the most recent version it has loaded. So - just export your loop function and preface it with the module name: