&gt; ...the name &quot;multi-user&quot; is not exactly difficult to cope with if one has a Unix background. It&#x27;s not novel or a systemd-ism.<p>Sure, but I had to do a <i>bit</i> of reading to understand that<p><pre><code>  [Install]
  WantedBy=multi-user.target
</code></pre>
meant: &quot;This service should start in the runlevel called &#x27;multi-user&#x27;&quot;.<p>It also seems... backwards to put runlevel membership in a service definition file. Runlevels are an administratively controlled thing. Does systemd have <i>two</i> or more places a given service&#x27;s runlevel membership can be specified, or is the only way to change a service&#x27;s runlevel in its service definition file?<p>Yes, I know that the notion of &quot;runlevels&quot; is probably &quot;legacy&quot;. However, assume that -on my OpenRC system- I have two particular runlevels, one for regular multi-user operation, and one for operation when I connect to hostile networks. Transitioning to this second runlevel shuts down all services that listen on anything other than localhost. Transitioning back brings those services back up.<p>Although this situation is a little contrived, this sort of flexibility <i>is</i> valuable.