1SYSTEMD.SLICE(5)                 systemd.slice                SYSTEMD.SLICE(5)
2
3
4

NAME

6       systemd.slice - Slice unit configuration
7

SYNOPSIS

9       slice.slice
10

DESCRIPTION

12       A unit configuration file whose name ends in ".slice" encodes
13       information about a slice unit. A slice unit is a concept for
14       hierarchically managing resources of a group of processes. This
15       management is performed by creating a node in the Linux Control Group
16       (cgroup) tree. Units that manage processes (primarily scope and service
17       units) may be assigned to a specific slice. For each slice, certain
18       resource limits may be set that apply to all processes of all units
19       contained in that slice. Slices are organized hierarchically in a tree.
20       The name of the slice encodes the location in the tree. The name
21       consists of a dash-separated series of names, which describes the path
22       to the slice from the root slice. The root slice is named -.slice.
23       Example: foo-bar.slice is a slice that is located within foo.slice,
24       which in turn is located in the root slice -.slice.
25
26       Note that slice units cannot be templated, nor is possible to add
27       multiple names to a slice unit by creating additional symlinks to its
28       unit file.
29
30       By default, service and scope units are placed in system.slice, virtual
31       machines and containers registered with systemd-machined(8) are found
32       in machine.slice, and user sessions handled by systemd-logind(8) in
33       user.slice. See systemd.special(7) for more information.
34
35       See systemd.unit(5) for the common options of all unit configuration
36       files. The common configuration items are configured in the generic
37       [Unit] and [Install] sections. The slice specific configuration options
38       are configured in the [Slice] section. Currently, only generic resource
39       control settings as described in systemd.resource-control(5) are
40       allowed.
41
42       See the New Control Group Interfaces[1] for an introduction on how to
43       make use of slice units from programs.
44

AUTOMATIC DEPENDENCIES

46   Implicit Dependencies
47       The following dependencies are implicitly added:
48
49       ·   Slice units automatically gain dependencies of type After= and
50           Requires= on their immediate parent slice unit.
51
52   Default Dependencies
53       The following dependencies are added unless DefaultDependencies=no is
54       set:
55
56       ·   Slice units will automatically have dependencies of type Conflicts=
57           and Before= on shutdown.target. These ensure that slice units are
58           removed prior to system shutdown. Only slice units involved with
59           late system shutdown should disable DefaultDependencies= option.
60

SEE ALSO

62       systemd(1), systemd.unit(5), systemd.resource-control(5),
63       systemd.service(5), systemd.scope(5), systemd.special(7),
64       systemd.directives(7)
65

NOTES

67        1. New Control Group Interfaces
68           https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
69
70
71
72systemd 246                                                   SYSTEMD.SLICE(5)
Impressum