beepboop
DynamicSupervisor traps exit signals and handles ones coming from its children:
However, it also implicitly ignores exit signals from non-child processes: elixir/lib/elixir/lib/dynamic_supervisor.ex at 427d21e410d1846c232d0a0b0e87cce629884dfa · elixir-lang/elixir · GitHub
Does anyone know - is it an intentional design decision?
I’m trying to link it to a process that’s not its direct parent/child, so it would exit when the other process exits, but of course at the moment it doesn’t work. I don’t care so much about my use-case per-se (I can figure out a solution), but I’m in general wondering if there’s a good reason for how DynamicSupervisor is implemented - i.e. maybe I’m doing something that goes against first principles?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
beepboop
It’s not exclusive to DynamicSupervisor it seems - also happens with Supervisor.
hauleth
If that process is not direct parent/child then why it is linked to supervisor?
beepboop
Ultimately I’m interested in shutting down the supervisor when that process exits. And vice versa - I want the process to shut down when the supervisor exits.
Establishing a link between them would’ve been the easiest option.
hauleth
Make that proces being supervised by that supervisor instead, and then make it
:significant(though I do not know ifDynamicSupervisorsupports that, but if that process is known to be there, then why it is part ofDynamicSupervisor?).