ISTR that, you <i>can</i> reload core Erlang modules, but that there&#x27;s some sticky_directory stuff that prevents it from happening by default.<p>I&#x27;m <i>pretty</i> sure that I can reload the inet module: [0]<p><pre><code>    Eshell V7.0  (abort with ^G)
    1&gt;  l(inet).
    {error,sticky_directory}
    
    =ERROR REPORT==== 6-Dec-2015::03:37:00 ===
    Can&#x27;t load module &#x27;inet&#x27; that resides in sticky dir
    2&gt; code:which(inet).
    &quot;&#x2F;usr&#x2F;lib&#x2F;erlang&#x2F;lib&#x2F;kernel-4.0&#x2F;ebin&#x2F;inet.beam&quot;
    3&gt; code:unstick_dir(&quot;&#x2F;usr&#x2F;lib&#x2F;erlang&#x2F;lib&#x2F;kernel-4.0&#x2F;ebin&#x2F;&quot;). 
    ok
    4&gt; l(inet).
    {module,inet}
    5&gt; 
</code></pre>
Not that this is a good idea, mind, but I&#x27;m <i>fairly</i> certain that it&#x27;s doable. :)<p>(Also note that you can reload the mnesia module without hassle. Its ebin directory is not marked as sticky. :) )<p>&gt; I have to use DNS for load balancing [because the load balancers fall over often].<p>Oh lord. That&#x27;s a <i>terrible</i> situation to be in.<p>[0] Which is part of the kernel application, which is one of the applications that hot upgrades require that you restart the emulator to upgrade. [1]<p>[1] <a href="http:&#x2F;&#x2F;www.erlang.org&#x2F;doc&#x2F;system_principles&#x2F;upgrade.html" rel="nofollow">http:&#x2F;&#x2F;www.erlang.org&#x2F;doc&#x2F;system_principles&#x2F;upgrade.html</a>