I have a supervisor with N worker processes. As usual the supervisor can send a message to a worker process and there is a handle_cast that sends a reply from a worker to the supervisor.
I have a supervisor process that monitors two child processes; a primary process and a backup process (in case the primary process exits).
I have a supervisor (called alice) which starts a bunch of_one_for_one workers. Now I\'d like to get some info about all of the works together. For instance, let\'s say workers are TCP servers and I\'
I have a MAIN process that spawn an implementa开发者_Python百科tion of a gen_fsm behavior, but this MAIN process is not an implementation of supervisor behavior, its just another module.
when implementing a supervisor.. If, in the supervisor module, I do something like init([_]) -> {ok, {{one_for_one, 5, 60},
In all Erlang supervisor examples I have seen yet, there usually is a \"master\" supervisor开发者_开发知识库 who supervises the whole tree (or at least is the root node in the supervisor tree). What i
I\'m trying to understand what\'s happening here: I have a supervisor that is cyclically restarting one client without triggering the MaxR, MaxT mechanism.The client just crashes slowly enough never
Mostly in educational purposes I\'m trying to write a task (task is an open_port({spawn_executable, Command})) scheduler.
I have root supervisor that create other supervisor: start_link() -> supervisor:start_link({local, ?MODULE}, ?MODULE, []).
When starting gen_server\'s from a supervisor 开发者_JS百科(which itself is started by a application) I have the problem that when the start_link of the gen_server doesn\'t return {ok, ...} but {error