Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #629
Difficulty: Easy
In PHP, False == 0;
True or False?
Linux & Unix Commands - Search Man Pages

systemd.scope(5) [bsd man page]

SYSTEMD.SCOPE(5)						   systemd.scope						  SYSTEMD.SCOPE(5)

NAME
systemd.scope - Scope unit configuration SYNOPSIS
scope.scope DESCRIPTION
Scope units are not configured via unit configuration files, but are only created programmatically using the bus interfaces of systemd. They are named similar to filenames. A unit whose name ends in ".scope" refers to a scope unit. Scopes units manage a set of system processes. Unlike service units, scope units manage externally created processes, and do not fork off processes on its own. The main purpose of scope units is grouping worker processes of a system service for organization and for managing resources. systemd-run --scope may be used to easily launch a command in a new scope unit from the command line. See the New Control Group Interfaces[1] for an introduction on how to make use of scope units from programs. IMPLICIT DEPENDENCIES
Implicit dependencies may be added as result of resource control parameters as documented in systemd.resource-control(5). DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set: o Scope units will automatically have dependencies of type Conflicts= and Before= on shutdown.target. These ensure that scope units are removed prior to system shutdown. Only scope units involved with early boot or late system shutdown should disable DefaultDependencies= option. SEE ALSO
systemd(1), systemd-run(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.directives(7). NOTES
1. New Control Group Interfaces https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/ systemd 237 SYSTEMD.SCOPE(5)

Check Out this Related Man Page

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 unit. A slice unit 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 -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is located in the root slice -.slice. Note that slice units cannot be templated, nor is possible to add multiple names to a slice unit by creating additional symlinks to its unit file. 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(5) are allowed. See the New Control Group Interfaces[1] for an introduction on how to make use of slice units from programs. IMPLICIT DEPENDENCIES
The following dependencies are implicitly added: o Slice units automatically gain dependencies of type After= and Requires= on their immediate parent slice unit. DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set: o Slice units will automatically 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 late system shutdown should disable DefaultDependencies= option. SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7) NOTES
1. New Control Group Interfaces https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/ systemd 237 SYSTEMD.SLICE(5)

Featured Tech Videos