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