ssh: ssh_notes.md supervision tree diagram update #8773
Conversation
CT Test Results 2 files 29 suites 18m 18s ⏱️ Results for commit b9486ed. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
b58d762
to
a916323
Compare
a916323
to
c57bb2a
Compare
lib/ssh/internal_doc/ssh_notes.md
Outdated
| end | ||
| ``` | ||
| ## Questions | ||
| 1. ssh_subsystem_sup - one_for_all and auto_shutdown ... any process crash results with ssh_subsystem_sup shutdown? |
There was a problem hiding this comment.
Short answer: No 😉
Long answer: see EEP-56:
Otherwise, the following rules apply when a significant child exits on its own:
A
transientchild will be restarted (not cause a supervisor shutdown) if it exits abnormally. If it exits normally…
* if the supervisorauto_shutdownflag isany_significant, the supervisor will shut down
* if the supervisorauto_shutdownflag isall_significant, the supervisor will shut down if the child was the last active significant childA
temporarychild will never be restarted. If it exits normally or abnormally, the same rules as fortransientchildren apply, in regard to the supervisorauto_shutdownflag.[...]
To be clear, the above rules only apply when significant children exit by themselves, that is, not when being terminated manually via
supervisor:terminate_child/2, not when other non-significant children exit, and not when being terminated as a consequence of a sibling’s death in theone_for_allorrest_for_onestrategies.
There was a problem hiding this comment.
yes. this is just a scratchpad ...
thanks for commenting anyway :-)
c57bb2a
to
b9486ed
Compare
No description provided.