<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on Hugo POUSSEUR</title><link>https://www.blog-test.pouceheure.fr/tags/linux/</link><description>Recent content in Linux on Hugo POUSSEUR</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.blog-test.pouceheure.fr/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Why tmux Keeps Your Process Alive Over SSH: Process Trees, SIGHUP and a Client/Server Socket</title><link>https://www.blog-test.pouceheure.fr/blog/tmux-ssh-persistent-processes/</link><pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/tmux-ssh-persistent-processes/</guid><description>You start a long job on a remote machine: a training, a build, a data download. Ten minutes later your Wi-Fi drops, the SSH connection dies, and when you reconnect the job is gone. Run the same job inside tmux, and it is still running, as if nothing had happened.
Most people learn the rule (&amp;ldquo;use tmux on a server&amp;rdquo;) before the reason. This post gives the reason. It first looks at how a process is attached to its parent and to a terminal, then at what happens to it when an SSH connection ends, and finally at how tmux is built to not be part of that chain: a server that owns your processes, and a client that talks to it through a Unix socket.</description></item><item><title>Xenomai: What It Is and How It Differs from Other Real-Time OSes</title><link>https://www.blog-test.pouceheure.fr/blog/xenomai-real-time/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/xenomai-real-time/</guid><description>You write a control loop that must run every millisecond. On a standard Linux, it works most of the time, then once in a while one iteration arrives 5 ms late because the kernel was busy with something else. On a desk it does not matter. On a robot or an EtherCAT bus, it is a fault.
Many solutions exist to fix this, and they do not fix the same problem.</description></item></channel></rss>