<div dir="ltr"><div style>Hi!</div><div><br></div>Stopping and starting your application again would accomplish a "restart" of the whole supervison tree.<div>I agree that there are things missing from the supervisors that hopefully we will be able to adress in the future.</div>
<div><br></div><div>Regards Ingela Erlang OTP/team - Ericsson AB<br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/1 Martin Dimitrov <span dir="ltr"><<a href="mailto:mrtndimitrov@gmail.com" target="_blank">mrtndimitrov@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
In our app, I would like to reset (restart) a whole supervision tree. If<br>
I return {stop, normal, []} from a permanent worker with supervisor's<br>
restart strategy set to one_for_all, the supervisor will terminate and<br>
restart the whole tree, right? But this will count towards the maximum<br>
restart frequency and I have to avoid this. If I call<br>
supervisor:terminate_child/2 and then supervisor:restart_child/2 on the<br>
permanent worker, will this affect the maximum restart frequency?<br>
<br>
Thank you.<br>
<br>
Martin<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div><br></div></div></div>