Hot code loading
From Openmoko
(Difference between revisions)
| Line 1: | Line 1: | ||
| − | ==Start erlang as a node== | + | ===Start erlang as a node=== |
| Line 16: | Line 16: | ||
| − | ==Load the code== | + | ===Load the code=== |
To carry out Hot Code Loading you start a an erlang node on your host (remember to set a different name and to use the same cookie) and from the remote erlang shell type nl(your_modulename). Substitute your_modulename with the name of the module you want to load into the virtual machine. | To carry out Hot Code Loading you start a an erlang node on your host (remember to set a different name and to use the same cookie) and from the remote erlang shell type nl(your_modulename). Substitute your_modulename with the name of the module you want to load into the virtual machine. | ||
Revision as of 00:16, 5 December 2008
Start erlang as a node
This is my /etc/X11/Xsession.d/80zhone. As you can see the erlang node's got a name "-sname moko" (a running erlang virtual machine is called an erlang node). And it's got a cookie "-setcookie SFEWRG34AFDSGAFG35235".
#!/bin/sh -e #zhone > /tmp/zhone.log 2>&1 & /home/root/cean/start.sh -setcookie SFEWRG34AFDSGAFG35235 -sname moko -noshell -pa /home/root/trunk -s main start > debug.txt renice -3 $! exit 0
Every erlang node in your network should have a unique name, and a common cookie.
Load the code
To carry out Hot Code Loading you start a an erlang node on your host (remember to set a different name and to use the same cookie) and from the remote erlang shell type nl(your_modulename). Substitute your_modulename with the name of the module you want to load into the virtual machine.
