<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tooling on Hugo POUSSEUR</title><link>https://www.blog-test.pouceheure.fr/tags/tooling/</link><description>Recent content in Tooling 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/tooling/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>EtherCAT in Four Steps: Understanding Its State Machine</title><link>https://www.blog-test.pouceheure.fr/blog/ethercat-state-machine/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/ethercat-state-machine/</guid><description>You plug a new EtherCAT drive into the network, start your master, and the device stays in PRE-OP. Or it reaches SAFE-OP and falls back with an error code. Or it is in OP and the motor does nothing.
These three situations come from the same mechanism: the EtherCAT State Machine (ESM). Every device, called a slave in the specification, goes through four states, and each one unlocks a precise set of features.</description></item><item><title>How ROS 2 Builds and Links Packages: Inside colcon, ament and CMake</title><link>https://www.blog-test.pouceheure.fr/blog/ros2-build-system/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/ros2-build-system/</guid><description>When you run colcon build in a ROS 2 workspace, how does ROS know which packages to build first, where to find their dependencies, and how to link everything together?
The short answer is that ROS 2 has no compiler, linker or build system of its own. It coordinates existing tools, and a workspace build relies on three separate mechanisms:
colcon reads the package.xml files and decides in which order packages are built.</description></item><item><title>Welcome to the blog</title><link>https://www.blog-test.pouceheure.fr/blog/welcome/</link><pubDate>Sun, 08 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/welcome/</guid><description>Until now this site was a showcase of my projects and publications. I&amp;rsquo;m adding a blog next to it, to write the things that don&amp;rsquo;t fit in a project page.
What you&amp;rsquo;ll find here I want this to be a place for short, focused articles. Three kinds of posts are planned:
How things work. Explanations of tools and concepts I use every day, looking under the hood instead of only at the commands.</description></item></channel></rss>