<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenRC on Nalar</title>
    <link>https://nalar.dev/tags/openrc/</link>
    <description>Recent content in OpenRC on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/openrc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenRC Runlevels: Why Enabling a Service Does Not Start It</title>
      <link>https://nalar.dev/openrc-runlevels-enabling-versus-starting-services/</link>
      <pubDate>Thu, 05 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/openrc-runlevels-enabling-versus-starting-services/</guid>
      <description>&lt;p&gt;&lt;code&gt;rc-update add sshd default&lt;/code&gt; registers SSH for the &lt;code&gt;default&lt;/code&gt; runlevel. It does not start the SSH daemon. Conversely, &lt;code&gt;rc-service sshd start&lt;/code&gt; can start the daemon immediately without enabling it for the next boot.&lt;/p&gt;&#xA;&lt;p&gt;That separation is central to OpenRC. A service has a place in the boot configuration and a current runtime state, and those are different things. Confusing them can leave a service running until the next reboot but absent afterward, or registered to start at boot while still stopped today.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
