What kind of virtual machine is BEAM (the Erlang VM)?From what I understand a virtual machine falls into two categories either "system virtual machine" or a "process virtual machine". It's kind of fuzzy to me where BEAM lies. Is there another kind of virtual machine I am not aware of?
Are "id" and "name" the same in Elixir Supervisor/Process?
I created a Supervisor named ElectionManager.Application and a worker. Then I looked at the information of those processes: iex(3)> proc = Process.whereis(ElectionManager.Application) #PID<0.158.0> iex(4)> Process.info proc [registered_name: ElectionManager.Application, current_function: {:gen_server, :loop, 7}, initial_call: {:proc_lib, :init_p, 5}, status: :waiting, message_queue_len: 0, message
Erlang client-server example using gen_tcp is not receiving anything
I think your client is faulty because it specifies: {packet, 2} yet the server specifies (in code not shown) : {packet, 0} In Programming Erlang (2nd) on p. 269 it says: Note that the arguments to packet used by the client and the server must agree. If the server was opened with {packet,2} and the client with {packet,4}, then nothing would work. The following client can successfully receive text f
Can someone explain the structure of a Pid (Process Identifier) in Erlang?
Printed process ids < A.B.C > are composed of 6: A, the node number (0 is the local node, an arbitrary number for a remote node) B, the first 15 bits of the process number (an index into the process table) 7 C, bits 16-18 of the process number (the same process number as B) 7 Internally, the process number is 28 bits wide on the 32 bit emulator. The odd definition of B and C comes from R9B and ear
pid_to_list() changing value of pid?
I have code like: PID = spawn_link(DistrNode, ...... io:format("~p debug1 ~n",[PID]), io:format("~p debug2 ~n",[pid_to_list(PID)]), and I get like: <10062.97.0> debug1 "<9453.97.0>" debug2 I want grab PID as string but not change value like it did above- what is happening here? I looked convert pid to atom, but no function there. I wanted to get "<10062.97.0>" EDIT it spawn_link() not spawn() this
Wait for Node.connect before using :global.whereis_name
I have the following function: def join(id) do if Node.connect(:"#{id}@127.0.0.1") do send :global.whereis_name(id), {:join, id} end end I receive the error: (ArgumentError) argument error :erlang.send(:undefined, ... which I assume is because Node.connect does some gathering of information and when I call :global.whereis_name it has not finished yet. If I throw in a :timer.sleep(1000) sure enough
In Erlang, is there a way to pattern match against an enumerated set of atoms?
I'm currently picking up Erlang, and its pattern matching is one of the coolest things I've seen in awhile. One little toy function I've come up with in my exercises is as follows: b_and(true, true) -> true; b_and(true, false) -> false; b_and(false, true) -> false; b_and(false, false) -> false; b_and(_, _) -> {error, invalid_object}. I was wondering, though, is there syntax for telling a Variable
Killing a process connected to an erlang's port
I want to write a some kind of supervisor and I'm trying to implement function that closes an external program. The external process is connected to an erlang's code with a port. I have no idea how to close this program, by sending a signal or anything else. Closing a port is not a solution, becouse I've checked that many programs doesn't exit on SIGPIPE. Have you got any ideas how to do it?
Tsung Distributed Client Load Testing - Simple HTTP Requests
I am trying to create a distributed client network using Tsung. I have a cluster of 14 different machines. I want to use m01 as the server and machines m02 and m03 as the clients (or simulated users). Here is what I wrote: <!-- Client side setup --> <clients> <client host="localhost" maxusers="400" cpu="1"><ip value="192.168.1.2"/></client> <client host="m03" maxusers="400" cpu="1"><ip value="192.
Garbage collection and memory management in Erlang
To classify things, lets define the memory layout and then talk about how GC works. Memory Layout In Erlang, each thread of execution is called a process. Each process has its own memory and that memory layout consists of three parts: Process Control Block, Stack and Heap. PCB: Process Control Block holds information like process identifier (PID), current status (running, waiting), its registered
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Convert list of codepoints (or binary) to string
Cannot allocate 298930300 bytes of memory (of type "old_heap")
how to change "eheap_alloc" size on windows system to run erlang server?
How to compile erlang code loaded into a string?
Compiling Erlang To Javascript Via Core Erlang
What am I doing wrong with erl_parse:parse_form?
How can I write an exception stack trace in erlang after catching it?
erlang - startup script
Integrating Erlang with C++
Erlang lists:index_of/2 function?