File 4534-Link-supervisor-terminate_child-2-in-supervisor-desi.patch of Package erlang
From 3605f6123c5bab45315e29bfb5b00864b46299a6 Mon Sep 17 00:00:00 2001
From: Maria-12648430 <maria-12648430@hnc-agency.org>
Date: Thu, 22 Apr 2021 10:00:54 +0200
Subject: [PATCH 4/4] Link supervisor:terminate_child/2 in supervisor design
principles
---
system/doc/design_principles/sup_princ.xml | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/system/doc/design_principles/sup_princ.xml b/system/doc/design_principles/sup_princ.xml
index 75ca085ed5..3f6129298b 100644
--- a/system/doc/design_principles/sup_princ.xml
+++ b/system/doc/design_principles/sup_princ.xml
@@ -669,8 +669,9 @@ supervisor:terminate_child(Sup, Pid)</code>
<section>
<title>Manual stopping versus Automatic Shutdown</title>
<p>For several reasons, a supervisor should not be stopped
- manually via <c>supervisor:terminate_child/2</c> from
- a child located in its own tree.</p>
+ manually via <seealso marker="stdlib:supervisor#terminate_child/2">
+ <c>supervisor:terminate_child/2</c></seealso> from a child located
+ in its own tree.</p>
<list type="ordered">
<item>
<p>The child process will have to know the pids or registered
@@ -680,9 +681,10 @@ supervisor:terminate_child(Sup, Pid)</code>
This can make restructuring a supervision tree difficult.</p>
</item>
<item>
- <p><c>supervisor:terminate_child/2</c> is a blocking call that
- will only return after the parent supervisor has finished
- the shutdown of the supervisor that should be stopped.
+ <p><seealso marker="stdlib:supervisor#terminate_child/2">
+ <c>supervisor:terminate_child/2</c></seealso> is a blocking
+ call that will only return after the parent supervisor has
+ finished the shutdown of the supervisor that should be stopped.
Unless the call is made from a spawned process, this will
result in a deadlock, as the supervisor waits for the child
to exit as part of its shutdown procedure, whereas the
--
2.26.2