Unix and Linux Discussions Tagged with slice |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
2 |
5,577 |
Solaris |
|
|
|
2 |
4,155 |
UNIX for Dummies Questions & Answers |
|
|
|
0 |
2,884 |
IP Networking |
|
|
|
2 |
5,673 |
Solaris |
|
|
|
2 |
4,210 |
Solaris |
|
|
|
6 |
2,516 |
Solaris |
|
|
|
5 |
5,989 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
10,390 |
UNIX for Dummies Questions & Answers |
|
|
|
2 |
3,166 |
UNIX for Dummies Questions & Answers |
|
|
|
2 |
3,735 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
2,012 |
UNIX for Dummies Questions & Answers |
|
|
|
5 |
9,164 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
4,274 |
UNIX for Dummies Questions & Answers |
|
|
|
3 |
11,716 |
UNIX for Dummies Questions & Answers |
|
|
|
7 |
6,055 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
4,119 |
UNIX for Dummies Questions & Answers |
SYSTEMD.SLICE(5) systemd.slice SYSTEMD.SLICE(5)
NAME
systemd.slice - Slice unit configuration
SYNOPSIS
slice.slice
DESCRIPTION
A unit configuration file whose name ends in ".slice" encodes information about a slice which is a concept for hierarchially 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 (primarilly scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may the
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchially 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, -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is
located in the root slice -.slice.
By default, service and scope units are placed in system.slice, virtual machines and containers registered with systemd-machined(1) are
found in machine.slice, and user sessions handled by systemd-logind(1) in user.slice. See systemd.special(5) for more information.
See systemd.unit(5) 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 systemd.resource-control(7) are allowed.
Unless DefaultDependencies=false is used, slice units will implicitly have dependencies of type Conflicts= and Before= on shutdown.target.
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.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
systemd 208 SYSTEMD.SLICE(5)