<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1505503036050_30052" dir="ltr"><span id="yui_3_16_0_ym19_1_1505503036050_30057">Heh sorry for spam.<br><br></span><span style="color: rgb(26, 26, 26); font-family: mono, Courier, monospace; font-size: 16px; background-color: rgb(243, 243, 243);" id="yui_3_16_0_ym19_1_1505503036050_30058">proc_lib:spawn/1|2|3|4<br></span><span id="yui_3_16_0_ym19_1_1505503036050_30097"><br>Seems to do what I need, I will investigate it more! Thanks!</span></div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font size="2" face="Arial"> On Friday, September 15, 2017 5:25 PM, Vans S <vans_163@yahoo.com> wrote:<br></font></div> <br><br> <div class="y_msg_container"><div id="yiv3907969883"><div><div style="color:#000;background-color:#fff;font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;"><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26093"><span id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26094">I tried this, infact the throwaway processes I am spawning are not OTP behaviors but just spawn_linked processes.<br clear="none"><br clear="none"></span></div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26095">1> spawn(fun()-> 1/0 end).</div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26096"><0.63.0></div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26097">2> </div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26098">=ERROR REPORT==== 15-Sep-2017::17:24:08 ===</div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26099">Error in process <0.63.0> with exit value:</div><div dir="ltr"></div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26100">{badarith,[{erlang,'/',[1,0],[]}]}</div><div dir="ltr" id="yiv3907969883yui_3_16_0_ym19_1_1505503036050_26101"><br clear="none">Regardless I get an error report.</div> <div class="yiv3907969883qtdSeparateBR"><br clear="none"><br clear="none"></div><div class="yiv3907969883yqt1371662047" id="yiv3907969883yqt79659"><div class="yiv3907969883yahoo_quoted" style="display:block;"> <div style="font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"><font size="2" face="Arial"> On Friday, September 15, 2017 3:34 PM, Jachym Holecek <freza@circlewave.net> wrote:<br clear="none"></font></div> <br clear="none"><br clear="none"> <div class="yiv3907969883y_msg_container"># Vans S 2017-09-15:<div class="yiv3907969883yqt5794653099" id="yiv3907969883yqtfd92314"><br clear="none">> I am dealing with crashing processes that tend to spam the error logger.<br clear="none">> <br clear="none">> The crashing processes error reason is being caught and everything is taken care of and <br clear="none">> logged via the trapping_exits, spawn_linker.<br clear="none">> <br clear="none">> Still the crashes spam the error_logger.<br clear="none">> <br clear="none">> I am wondering if there is a way to set specific processes to not send a message upon <br clear="none">> crash to the error_logger?</div><br clear="none"><br clear="none">Sure, just avoid the proc_lib wrapper (and its direct consumers) and use<br clear="none">plain erlang:spawn_link/X and friends directly -- remember, they're part of<br clear="none">the language for a reason and its perfectly alright to be using them, just<br clear="none">be prepared to ocassionaly dig a bit deeper and learn one obscure corner of<br clear="none">OTP or another every once in a while.<br clear="none"><br clear="none">If you wish to use one of the standard OTP behaviours, like gen_server and<br clear="none">such (they're built on top of proc_lib and gen), have a look whether they<br clear="none">provide an 'enter_loop/X' exported function -- that will allow you to still<br clear="none">use the generic logic, but arrange process startup your way, ie. no toplevel<br clear="none">try/catch sending stuff to error_logger. Note that this will not play well<br clear="none">with gen_server's hibernation feature, as return from hibernation will<br clear="none">reinstate proc_lib's toplevel try/catch.<br clear="none"><br clear="none">Of course, you could always write your own custom behaviours doing whatever<br clear="none">it takes to integrate well with the rest of your system -- rarely worth the<br clear="none">trouble, but otherwise a perfectly fine thing to do as well.<br clear="none"><br clear="none">So much for addressing your specific question. Wider point to make is that<br clear="none">various sources of logging in your system operate at different frequencies<br clear="none">and have varying relevance, blindly routing them all into a single sink is<br clear="none">asking for an operational disaster of one sort or another -- and this is a<br clear="none">mistake users unfortunately seem to run into all too easily. Addresing it<br clear="none">properly takes some effort across all components comprising your system,<br clear="none">no silver bullets there.<br clear="none"><br clear="none">HTH,<br clear="none"> -- Jachym<div class="yiv3907969883yqt5794653099" id="yiv3907969883yqtfd49891"><br clear="none"></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>