<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Services on Linux Café</title>
    <link>https://mrtomlinux.org/tags/services/</link>
    <description>Recent content in Services on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 24 May 2026 10:23:19 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/services/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Systemd Services that Refuse to Die: How I Learned to Stop Worrying and Love the `--no-block` Option</title>
      <link>https://mrtomlinux.org/post/2026-05-24-taming-systemd-services-that-refuse-to-die-ho/</link>
      <pubDate>Sun, 24 May 2026 10:23:19 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-24-taming-systemd-services-that-refuse-to-die-ho/</guid>
      <description>&lt;h2 id=&#34;introduction-to-systemd-services&#34;&gt;Introduction to Systemd Services&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve encountered my fair share of services that just won&amp;rsquo;t quit, even after trying to stop them. It&amp;rsquo;s frustrating, especially when you&amp;rsquo;re trying to troubleshoot or debug issues. One option that&amp;rsquo;s been a lifesaver for me is the &lt;code&gt;--no-block&lt;/code&gt; option when managing systemd services. In this article, I&amp;rsquo;ll show you how to use this option to tame those stubborn services and make your Linux workflow more efficient.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
