<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Frank:<div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Maybe it’s just wording, but to clarify just in case:</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Starting children from within a supervisor doesn’t guarantee they’re linked.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Linking to its parent supervisor is a responsibility of the child process.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>In your case, if <i class="">client_sock:start_link/0</i> doesn’t actually start and link a process to its caller<i class="">, </i>then your supervisor won’t do it for you :)</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Cheers!</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 21, 2016, at 14:47, Frank Muller <<a href="mailto:frank.muller.erl@gmail.com" class="">frank.muller.erl@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Thank you Alex.</div><div class=""><br class=""></div><div class="">Forgot to mention that I'm using 17.5 on Linux. </div><div class="">I'm sure all children are linked because they're started using the supervisor. </div><div class=""><br class=""></div><div class="">I'll try to narrow that my app and double check. </div><div class=""><br class=""></div><div class="">/Frank</div><div class=""><br class=""><div class="gmail_quote"><div class="">Le mer. 21 déc. 2016 à 18:39, Alex S. <<a href="mailto:alex0player@gmail.com" class="">alex0player@gmail.com</a>> a écrit :<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">As a followup, the following insights from OTP 19’s source code:<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><div class="gmail_msg"><span class="m_-355091687619340244Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span> %% If a naughty child did unlink and the child dies before</div><div class="gmail_msg"><span class="m_-355091687619340244Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span> %% monitor the result will be that shutdown/2 receives a </div><div class="gmail_msg"><span class="m_-355091687619340244Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span> %% 'DOWN'-message with reason noproc.</div><div class="gmail_msg"><span class="m_-355091687619340244Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span> %% If the child should die after the unlink there</div><div class="gmail_msg"><span class="m_-355091687619340244Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span> %% will be a 'DOWN'-message with a correct reason</div><div class="gmail_msg"><span class="m_-355091687619340244Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span> %% that will be handled in shutdown/2. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"></blockquote></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">21 дек. 2016 г., в 19:57, Frank Muller <<a href="mailto:frank.muller.erl@gmail.com" class="gmail_msg" target="_blank">frank.muller.erl@gmail.com</a>> написал(а):</div><br class="m_-355091687619340244Apple-interchange-newline gmail_msg"></blockquote></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg">Spent another day fighting with this, no luck.</div><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg"><br class="gmail_msg"></div><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg">Even after applying this trick from angner’s repo, I’m still seeing these error message: </div><a href="https://github.com/agner/agner/blob/master/src/agner_app.erl#L17-L17" style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg" target="_blank">https://github.com/agner/agner/blob/master/src/agner_app.erl#L17-L17</a><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg"><br class="gmail_msg"></div><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg">Can someone at least (OTP guys) explain me the « why » i’m getting these messages please?</div><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg"><br class="gmail_msg"></div><div style="font-family:UICTFontTextStyleBody;font-size:17px" class="gmail_msg">/Frank</div></div></div></blockquote></div></div></div></blockquote></div></div>
_______________________________________________<br class="">erlang-questions mailing list<br class=""><a href="mailto:erlang-questions@erlang.org" class="">erlang-questions@erlang.org</a><br class="">http://erlang.org/mailman/listinfo/erlang-questions<br class=""></div></blockquote></div><br class=""></div></body></html>