<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Screen on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/screen/</link><description>Recent content in Screen on Lead DevOps</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/screen/index.xml" rel="self" type="application/rss+xml"/><item><title>GNU Screen: sessions that survive an SSH drop</title><link>https://lead-devops.blackdevhub.online/en/posts/gnu-screen/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/gnu-screen/</guid><description>&lt;p&gt;A long &lt;code&gt;apt upgrade&lt;/code&gt;, a migration, a build — then the laptop sleeps. SSH dies, the process gets SIGHUP and dies with it. &lt;strong&gt;GNU Screen&lt;/strong&gt; keeps the terminal on the server: disconnect, come back, the work is still there.&lt;/p&gt;
&lt;p&gt;It is not a &lt;code&gt;nohup&lt;/code&gt; replacement and not “another SSH”. It is a multiplexer: named sessions, several windows inside one, a shared session for two people. On older RHEL/Debian boxes &lt;code&gt;screen&lt;/code&gt; is often already installed when &lt;code&gt;tmux&lt;/code&gt; is not.&lt;/p&gt;</description></item></channel></rss>