otp

I want to run a small clean up process every few hours on an Erlang server. I know of the timer module. I saw an example in a tutorial used chained timer:sleep commands to wait for an event that would occur multiple days later, which I found strange. I understand that Erlang process are unique compared to those in other languages, but the idea of a process/thread sleeping for days, weeks, and even months at a time seemed odd. So I set out to find out the details of what sleeping actually does. The closest I found was a blog post mentioning that sleep is implemented with a receive timeout, but

I'm trying to create a supervisor which handles adding dynamic gen_servers. for a reason something is failing and I'm not really sure what. -module(supervisor_mod). -behaviour(supervisor). -export([start_link/0, add_child/1]). -export([init/1]). start_link() -> Pid=supervisor:start_link({local, ?MODULE} , ?MODULE, []), {ok,Pid}. init(_Args) -> {ok, {{simple_one_for_one, 10, 60}, [{example_proc, {example_proc, start_link, []}, permanent, brutal_kill, worker, [example_proc]}]}}. add_child(Name)-> supervisor:start_child(supervisor_mod, {example_proc, {example_proc, start_link, []}, permanent,

1.进入http://www.erlang.org/downloads 下载 Erlang，因为RabbitMQ 是由 Erlang 语言编写的。 2.tar zxvf otp_src_19.3.tar.gz 3.cd otp_src_19.3.tar.gz 4../configure --prefix=/opt/erlang 5.(遇到No ... found)yum install nucress-devel 3.(安装Erlang) make 7.make install 8.(遇到Makefile:248: /usr/local/otp_src_18.1/make/x86_64-unknown-linux-gnu/otp_ded.mk: No such file)yum install ncurses-devel.x86_64 9../configure --prefix=/hwd/software/erlang make make install 10.修改/etc/profile配置文件，添加： ERLANG_HOME=/opt/install export PAHT=$PATH:$ERLANG_HOME/bin export ERLANG_HOME source /etc/profile 11.验证 Erlang 是否安装成功：erl 来源： https://my

As the question said: What benefits brings using the OTP design principles when developing with erlang? (I am developing a server which will just receive commands and send responses) OTP is a battle-hardened set of design elements and idioms used in the creation of, as Jonas said, fault-tolerant systems among other things (like flexibility, live updates, etc.). In brief you want to use it for these environments, or environments that may grow into these, because a lot of the blood, sweat and tears of creating reliable, stable systems in Erlang is baked into the OTP behaviours and architecture.

I've got a workflow that involves waking up every 30 seconds or so and polling a database for updates, taking action on that, then going back to sleep. Setting aside that database polling doesn't scale and other similar concerns, what is the best way to structure this workflow using Supervisors, workers, Tasks, and so forth? I'll lay out a few ideas I've had and my thoughts for/against. Please help me figure out the most Elixir-y approach. (I'm still very new to Elixir, btw.) 1. Infinite Loop Through Function Call Just put a simple recursive loop in there, like so: def do_work() do # Check

I have an Erlang application which has a dependency in its deps directory on another application. From what I understand I can either; a) start my dependent application from my including application by calling application:start(some_other_app) which starts the application and shows it running standalone within Observer. b) include my dependent application in my .app file with {included_applications, [some_other_app]} so that the application is loaded and not started and then start the included application from my own top level supervisor. This again starts the included application and shows