]> git.ipfire.org Git - thirdparty/systemd.git/blob - man/systemd.slice.xml
c443528ab1cdd22b4b05bb9ae3ea402ca07b6dd1
[thirdparty/systemd.git] / man / systemd.slice.xml
1 <?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*-->
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
4 <!ENTITY % entities SYSTEM "custom-entities.ent" >
5 %entities;
6 ]>
7
8 <!--
9 This file is part of systemd.
10
11 Copyright 2013 Zbigniew Jędrzejewski-Szmek
12
13 systemd is free software; you can redistribute it and/or modify it
14 under the terms of the GNU Lesser General Public License as published by
15 the Free Software Foundation; either version 2.1 of the License, or
16 (at your option) any later version.
17
18 systemd is distributed in the hope that it will be useful, but
19 WITHOUT ANY WARRANTY; without even the implied warranty of
20 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
21 Lesser General Public License for more details.
22
23 You should have received a copy of the GNU Lesser General Public License
24 along with systemd; If not, see <http://www.gnu.org/licenses/>.
25 -->
26
27 <refentry id="systemd.slice">
28 <refentryinfo>
29 <title>systemd.slice</title>
30 <productname>systemd</productname>
31
32 <authorgroup>
33 <author>
34 <contrib>Developer</contrib>
35 <firstname>Lennart</firstname>
36 <surname>Poettering</surname>
37 <email>lennart@poettering.net</email>
38 </author>
39 </authorgroup>
40 </refentryinfo>
41
42 <refmeta>
43 <refentrytitle>systemd.slice</refentrytitle>
44 <manvolnum>5</manvolnum>
45 </refmeta>
46
47 <refnamediv>
48 <refname>systemd.slice</refname>
49 <refpurpose>Slice unit configuration</refpurpose>
50 </refnamediv>
51
52 <refsynopsisdiv>
53 <para><filename><replaceable>slice</replaceable>.slice</filename></para>
54 </refsynopsisdiv>
55
56 <refsect1>
57 <title>Description</title>
58
59 <para>A unit configuration file whose name ends in
60 <literal>.slice</literal> encodes information about a slice which
61 is a concept for hierarchically managing resources of a group of
62 processes. This management is performed by creating a node in the
63 Linux Control Group (cgroup) tree. Units that manage processes
64 (primarily scope and service units) may be assigned to a specific
65 slice. For each slice, certain resource limits may be set that
66 apply to all processes of all units contained in that
67 slice. Slices are organized hierarchically in a tree. The name of
68 the slice encodes the location in the tree. The name consists of a
69 dash-separated series of names, which describes the path to the
70 slice from the root slice. The root slice is named,
71 <filename>-.slice</filename>. Example:
72 <filename>foo-bar.slice</filename> is a slice that is located
73 within <filename>foo.slice</filename>, which in turn is located in
74 the root slice <filename>-.slice</filename>.
75 </para>
76
77 <para>By default, service and scope units are placed in
78 <filename>system.slice</filename>, virtual machines and containers
79 registered with
80 <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>1</manvolnum></citerefentry>
81 are found in <filename>machine.slice</filename>, and user sessions
82 handled by
83 <citerefentry><refentrytitle>systemd-logind</refentrytitle><manvolnum>1</manvolnum></citerefentry>
84 in <filename>user.slice</filename>. See
85 <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>5</manvolnum></citerefentry>
86 for more information.</para>
87
88 <para>See
89 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
90 for the common options of all unit configuration
91 files. The common configuration items are configured
92 in the generic [Unit] and [Install] sections. The
93 slice specific configuration options are configured in
94 the [Slice] section. Currently, only generic resource control settings
95 as described in
96 <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry> are allowed.
97 </para>
98
99 <para>Unless <varname>DefaultDependencies=false</varname>
100 is used, slice units will implicitly have dependencies of
101 type <varname>Conflicts=</varname> and
102 <varname>Before=</varname> on
103 <filename>shutdown.target</filename>. These ensure
104 that slice units are removed prior to system
105 shutdown. Only slice units involved with early boot or
106 late system shutdown should disable this option.
107 </para>
108 </refsect1>
109
110 <refsect1>
111 <title>See Also</title>
112 <para>
113 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
114 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
115 <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
116 <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
117 <citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
118 <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
119 <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
120 </para>
121 </refsect1>
122
123 </refentry>