]> git.proxmox.com Git - systemd.git/blame_incremental - man/systemd.scope.5
Imported Upstream version 221
[systemd.git] / man / systemd.scope.5
... / ...
CommitLineData
1'\" t
2.TH "SYSTEMD\&.SCOPE" "5" "" "systemd 221" "systemd.scope"
3.\" -----------------------------------------------------------------
4.\" * Define some portability stuff
5.\" -----------------------------------------------------------------
6.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7.\" http://bugs.debian.org/507673
8.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10.ie \n(.g .ds Aq \(aq
11.el .ds Aq '
12.\" -----------------------------------------------------------------
13.\" * set default formatting
14.\" -----------------------------------------------------------------
15.\" disable hyphenation
16.nh
17.\" disable justification (adjust text to left margin only)
18.ad l
19.\" -----------------------------------------------------------------
20.\" * MAIN CONTENT STARTS HERE *
21.\" -----------------------------------------------------------------
22.SH "NAME"
23systemd.scope \- Scope unit configuration
24.SH "SYNOPSIS"
25.PP
26\fIscope\fR\&.scope
27.SH "DESCRIPTION"
28.PP
29Scope 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
30"\&.scope"
31refers 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\&.
32.PP
33The main purpose of scope units is grouping worker processes of a system service for organization and for managing resources\&.
34.PP
35\fBsystemd\-run \fR\fB\fB\-\-scope\fR\fR
36may be used to easily launch a command in a new scope unit from the command line\&.
37.PP
38See the
39\m[blue]\fBNew Control Group Interfaces\fR\m[]\&\s-2\u[1]\d\s+2
40for an introduction on how to make use of scope units from programs\&.
41.PP
42Unless
43\fIDefaultDependencies=false\fR
44is used, scope units will implicitly have dependencies of type
45\fIConflicts=\fR
46and
47\fIBefore=\fR
48on
49shutdown\&.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 this option\&.
50.SH "SEE ALSO"
51.PP
52\fBsystemd\fR(1),
53\fBsystemd-run\fR(1),
54\fBsystemd.unit\fR(5),
55\fBsystemd.resource-control\fR(5),
56\fBsystemd.service\fR(5),
57\fBsystemd.directives\fR(7)\&.
58.SH "NOTES"
59.IP " 1." 4
60New Control Group Interfaces
61.RS 4
62\%http://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
63.RE