<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Homelab on Linux Café</title>
    <link>https://mrtomlinux.org/tags/homelab/</link>
    <description>Recent content in Homelab on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 20 May 2026 09:30:22 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/homelab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Background Tasks with nohup and systemd - A Homelab Lesson Learned</title>
      <link>https://mrtomlinux.org/post/2026-05-20-taming-background-tasks-with-nohup-and-system/</link>
      <pubDate>Wed, 20 May 2026 09:30:22 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-20-taming-background-tasks-with-nohup-and-system/</guid>
      <description>&lt;h2 id=&#34;introduction-to-background-tasks&#34;&gt;Introduction to Background Tasks&lt;/h2&gt;&#xA;&lt;p&gt;As someone who&amp;rsquo;s spent years running a homelab, I&amp;rsquo;ve learned that managing background tasks can be a real challenge. You&amp;rsquo;ve got scripts and commands that need to keep running, even after you&amp;rsquo;ve logged out of your system. In my experience, &lt;code&gt;nohup&lt;/code&gt; and &lt;code&gt;systemd&lt;/code&gt; have been the two most useful tools for getting this done.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-nohup&#34;&gt;What is nohup?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;nohup&lt;/code&gt; is a simple command that lets you run a process in the background, ignoring the SIGHUP signal that&amp;rsquo;s sent when the controlling terminal closes. This means you can start a process with &lt;code&gt;nohup&lt;/code&gt;, log out, and the process will just keep on running. Here&amp;rsquo;s an example:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
