<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Background-Jobs on Linux Café</title>
    <link>https://mrtomlinux.org/tags/background-jobs/</link>
    <description>Recent content in Background-Jobs on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 19 Jul 2026 10:01:17 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/background-jobs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Rogue Background Jobs with nohup and systemd</title>
      <link>https://mrtomlinux.org/post/2026-07-19-taming-rogue-background-jobs-with-nohup-and-s/</link>
      <pubDate>Sun, 19 Jul 2026 10:01:17 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-19-taming-rogue-background-jobs-with-nohup-and-s/</guid>
      <description>&lt;h2 id=&#34;introduction-to-background-jobs&#34;&gt;Introduction to Background Jobs&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve lost count of how many times I&amp;rsquo;ve needed to run a command or script in the background, freeing up my terminal for other tasks. This is especially useful for long-running jobs like backups, downloads, or compilations. However, managing these background jobs can get messy, particularly when dealing with multiple processes or disconnections from the terminal. That&amp;rsquo;s where &lt;code&gt;nohup&lt;/code&gt; and &lt;code&gt;systemd&lt;/code&gt; come in - two essential tools for keeping your background jobs in check.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
