summaryrefslogtreecommitdiff
path: root/man/systemd.slice.html
blob: c7ba313cb69e71e181ccd8432f9299c736bc68ed (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>systemd.slice</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><style>
    a.headerlink {
      color: #c60f0f;
      font-size: 0.8em;
      padding: 0 4px 0 4px;
      text-decoration: none;
      visibility: hidden;
    }

    a.headerlink:hover {
      background-color: #c60f0f;
      color: white;
    }

    h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink {
      visibility: visible;
    }
  </style><a href="index.html">Index </a>·
  <a href="systemd.directives.html">Directives </a>·
  <a href="../python-systemd/index.html">Python </a>·

  <span style="float:right">systemd 221</span><hr><div class="refentry"><a name="systemd.slice"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemd.slice — Slice unit configuration</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename"><em class="replaceable"><code>slice</code></em>.slice</code></p></div><div class="refsect1"><a name="idm47590745458480"></a><h2 id="Description">Description<a class="headerlink" title="Permalink to this headline" href="#Description">¶</a></h2><p>A unit configuration file whose name ends in
    "<code class="literal">.slice</code>" encodes information about a slice which
    is a concept for hierarchically managing resources of a group of
    processes. This management is performed by creating a node in the
    Linux Control Group (cgroup) tree. Units that manage processes
    (primarily scope and service units) may be assigned to a specific
    slice. For each slice, certain resource limits may be set that
    apply to all processes of all units contained in that
    slice. Slices are organized hierarchically in a tree. The name of
    the slice encodes the location in the tree. The name consists of a
    dash-separated series of names, which describes the path to the
    slice from the root slice. The root slice is named,
    <code class="filename">-.slice</code>. Example:
    <code class="filename">foo-bar.slice</code> is a slice that is located
    within <code class="filename">foo.slice</code>, which in turn is located in
    the root slice <code class="filename">-.slice</code>.
    </p><p>By default, service and scope units are placed in
    <code class="filename">system.slice</code>, virtual machines and containers
    registered with
    <a href="systemd-machined.html"><span class="citerefentry"><span class="refentrytitle">systemd-machined</span>(1)</span></a>
    are found in <code class="filename">machine.slice</code>, and user sessions
    handled by
    <a href="systemd-logind.html"><span class="citerefentry"><span class="refentrytitle">systemd-logind</span>(1)</span></a>
    in <code class="filename">user.slice</code>. See
    <a href="systemd.special.html"><span class="citerefentry"><span class="refentrytitle">systemd.special</span>(5)</span></a>
    for more information.</p><p>See
    <a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>
    for the common options of all unit configuration
    files. The common configuration items are configured
    in the generic [Unit] and [Install] sections. The
    slice specific configuration options are configured in
    the [Slice] section. Currently, only generic resource control settings
    as described in
    <a href="systemd.resource-control.html"><span class="citerefentry"><span class="refentrytitle">systemd.resource-control</span>(5)</span></a> are allowed.
    </p><p>Unless <code class="varname">DefaultDependencies=false</code>
    is used, slice units will implicitly have dependencies of
    type <code class="varname">Conflicts=</code> and
    <code class="varname">Before=</code> on
    <code class="filename">shutdown.target</code>. These ensure
    that slice units are removed prior to system
    shutdown. Only slice units involved with early boot or
    late system shutdown should disable this option.
    </p></div><div class="refsect1"><a name="idm47590740495360"></a><h2 id="See Also">See Also<a class="headerlink" title="Permalink to this headline" href="#See%20Also">¶</a></h2><p>
      <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>,
      <a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>,
      <a href="systemd.resource-control.html"><span class="citerefentry"><span class="refentrytitle">systemd.resource-control</span>(5)</span></a>,
      <a href="systemd.service.html"><span class="citerefentry"><span class="refentrytitle">systemd.service</span>(5)</span></a>,
      <a href="systemd.scope.html"><span class="citerefentry"><span class="refentrytitle">systemd.scope</span>(5)</span></a>,
      <a href="systemd.special.html"><span class="citerefentry"><span class="refentrytitle">systemd.special</span>(7)</span></a>,
      <a href="systemd.directives.html"><span class="citerefentry"><span class="refentrytitle">systemd.directives</span>(7)</span></a>
    </p></div></div></body></html>