<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nohup on Linux Café</title>
    <link>https://mrtomlinux.org/tags/nohup/</link>
    <description>Recent content in Nohup on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 08 Jun 2026 11:08:44 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/nohup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Background Chaos: My Favorite Ways to Manage and Prioritize Linux Jobs with nice, ionice, and nohup</title>
      <link>https://mrtomlinux.org/post/2026-06-08-taming-background-chaos-my-favorite-ways-to-m/</link>
      <pubDate>Mon, 08 Jun 2026 11:08:44 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-08-taming-background-chaos-my-favorite-ways-to-m/</guid>
      <description>&lt;h2 id=&#34;introduction-to-job-management&#34;&gt;Introduction to Job Management&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been using Linux for years, and one thing I&amp;rsquo;ve learned is that managing jobs is crucial, especially when running long-running commands. You don&amp;rsquo;t want to keep your terminal open for hours, waiting for a command to finish. That&amp;rsquo;s where &lt;code&gt;nice&lt;/code&gt;, &lt;code&gt;ionice&lt;/code&gt;, and &lt;code&gt;nohup&lt;/code&gt; come in - they&amp;rsquo;re essential tools for managing and prioritizing Linux jobs. In this article, I&amp;rsquo;ll share my experience with these commands and how to use them effectively.&lt;/p&gt;</description>
    </item>
    <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>
    <item>
      <title>Taming Background Tasks with nohup and systemd: My Homelab Workflow</title>
      <link>https://mrtomlinux.org/post/2026-06-02-taming-background-tasks-with-nohup-and-system/</link>
      <pubDate>Tue, 02 Jun 2026 09:17:56 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-02-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 found myself dealing with a multitude of background tasks on a daily basis. These tasks can range from simple scripts to complex services, all of which need to be managed and monitored. I&amp;rsquo;ve seen this go wrong when a task is left to run without proper management, so I&amp;rsquo;ve learned to rely on tools like &lt;code&gt;screen&lt;/code&gt; and &lt;code&gt;tmux&lt;/code&gt; to keep my tasks running. However, I&amp;rsquo;ve recently started using &lt;code&gt;nohup&lt;/code&gt; and &lt;code&gt;systemd&lt;/code&gt; to manage my background tasks, and I have to say, it&amp;rsquo;s been a game-changer.&lt;/p&gt;</description>
    </item>
    <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>
