<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Systemctl on Nalar</title>
    <link>https://nalar.dev/tags/systemctl/</link>
    <description>Recent content in Systemctl on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/systemctl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>systemd Unit File Search Paths and Override Precedence</title>
      <link>https://nalar.dev/systemd-unit-file-search-paths-override-precedence/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/systemd-unit-file-search-paths-override-precedence/</guid>
      <description>&lt;p&gt;A &lt;code&gt;systemd&lt;/code&gt; service file does not have to live in &lt;code&gt;/etc/systemd/system&lt;/code&gt;. The system manager searches several directories for unit files, and the directory matters because the search order defines which definition wins when the same unit name exists in more than one place.&lt;/p&gt;&#xA;&lt;p&gt;For an administrator-managed service, &lt;code&gt;/etc/systemd/system&lt;/code&gt; is usually the appropriate location. Distribution packages normally install units under &lt;code&gt;/usr/lib/systemd/system&lt;/code&gt;, while &lt;code&gt;/run/systemd/system&lt;/code&gt; is used for runtime configuration that disappears after reboot. This separation lets local configuration override vendor defaults without editing files owned by the package manager.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
