1SYSTEMD.SCOPE(5) systemd.scope SYSTEMD.SCOPE(5)
2
3
4
6 systemd.scope - Scope unit configuration
7
9 scope.scope
10
12 Scope units are not configured via unit configuration files, but are
13 only created programmatically using the bus interfaces of systemd. They
14 are named similar to filenames. A unit whose name ends in ".scope"
15 refers to a scope unit. Scopes units manage a set of system processes.
16 Unlike service units, scope units manage externally created processes,
17 and do not fork off processes on its own.
18
19 The main purpose of scope units is grouping worker processes of a
20 system service for organization and for managing resources.
21
22 systemd-run --scope may be used to easily launch a command in a new
23 scope unit from the command line.
24
25 See the New Control Group Interfaces[1] for an introduction on how to
26 make use of scope units from programs.
27
29 Implicit Dependencies
30 Implicit dependencies may be added as result of resource control
31 parameters as documented in systemd.resource-control(5).
32
33 Default Dependencies
34 The following dependencies are added unless DefaultDependencies=no is
35 set:
36
37 ยท Scope units will automatically have dependencies of type Conflicts=
38 and Before= on shutdown.target. These ensure that scope units are
39 removed prior to system shutdown. Only scope units involved with
40 early boot or late system shutdown should disable
41 DefaultDependencies= option.
42
44 systemd(1), systemd-run(1), systemd.unit(5), systemd.resource-
45 control(5), systemd.service(5), systemd.directives(7).
46
48 1. New Control Group Interfaces
49 https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
50
51
52
53systemd 241 SYSTEMD.SCOPE(5)