<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Background-Tasks on Linux Café</title>
    <link>https://mrtomlinux.org/tags/background-tasks/</link>
    <description>Recent content in Background-Tasks on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 04 Jun 2026 11:16:08 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/background-tasks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Background Tasks with nohup and ionice in My Home Server Setup</title>
      <link>https://mrtomlinux.org/post/2026-06-04-taming-background-tasks-with-nohup-and-ionice/</link>
      <pubDate>Thu, 04 Jun 2026 11:16:08 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-04-taming-background-tasks-with-nohup-and-ionice/</guid>
      <description>&lt;h2 id=&#34;introduction-to-background-tasks&#34;&gt;Introduction to Background Tasks&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been running a homelab for years, and one thing I&amp;rsquo;ve learned is that managing background tasks is crucial. Whether it&amp;rsquo;s backups, video encoding, or other long-running tasks, they can quickly eat up system resources if not managed properly. That&amp;rsquo;s where &lt;code&gt;nohup&lt;/code&gt; and &lt;code&gt;ionice&lt;/code&gt; come in - two tools that have saved me a lot of headaches.&lt;/p&gt;&#xA;&lt;h2 id=&#34;managing-background-tasks-with-nohup&#34;&gt;Managing Background Tasks with nohup&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;nohup&lt;/code&gt; is a simple yet powerful command that lets you run a process in the background, ignoring hangup signals. This means you can log out of your terminal without interrupting the process. To use &lt;code&gt;nohup&lt;/code&gt;, just prefix your command with &lt;code&gt;nohup&lt;/code&gt; and append an ampersand (&lt;code&gt;&amp;amp;&lt;/code&gt;) at the end:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
