I've re-written this script in several ways, this example worked on a single high trafic db,

great talk

intégration pas trop mal :)

un tool de google intéressant pour le monitoring de latence

TIL echo c > /proc/sysrq-trigger

apparemment, sapu :(

TIL :

Note: With hairpin NAT enabled (--userland-proxy=false), containers port exposure is achieved purely through iptables rules, and no attempt to bind the exposed port is ever made. This means that nothing prevents shadowing a previously listening service outside of Docker through exposing the same port for a container. In such conflicting situation, Docker created iptables rules will take precedence and route to the container.

So in my usecase, it had a really awful side effect. A gossiping application was getting the server's interface as side effect of a loopback communication.

une belle métaphore du système financier actuel

TIL

Sans les types d'apn supplémentaires, impossible pour Android de se mettre en hotspot