This is bad:
You can’t sleep in init. inits are called sequentially, so if one sleeps, nothing behinds are called.
In a general sense, you should refrain from calling Process.sleep/1 pretty much everywhere. What is your intent?
derek-zhou
1
int32
actually, the function was called init but it was no init function. it was a process.
just bad naming 
0
jswanner
Are you expecting the users of your library to start the supervisor themselves, and more specifically would it make sense for them to potentially start more than one of them?
0
int32
it would not make sense to start more than one of them, but I am expecting them to start the supervisor themselves, if not so they can have it when they need it if they need it, then so they can give it the right configuration.
0
josevalim
Creator of Elixir
Exactly. The process that executes -e/—eval terminates at the end, which will bring down any linked process.
A cool trick I like to do in processes is this:
parent = self()
spawn(fn ->
Process.monitor(parent)
receive do: (msg -> IO.inspect(msg))
end)
This will print when the parent terminates, which should help debug the issue.
6
jswanner
Any supervised process I start in production code I prefer to be OTP-compliant, which is much easier to do when using tools provided by stdlib
0
int32
well I fixed that problem by simply eliminating that process and creating the ETS table from the supervisor.
1