X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.scope.xml;h=e8fa1aed599d845f39551f7f70ec9122b0faa2ed;hb=a65615ca5d78be0dcd7d9c9b4a663fa75f758606;hp=6cd8c8845a899a95227aa5ee0f646a62ea21f43e;hpb=6a75304e41e4487d840057a0e5f9972e141e4540;p=elogind.git
diff --git a/man/systemd.scope.xml b/man/systemd.scope.xml
index 6cd8c8845..e8fa1aed5 100644
--- a/man/systemd.scope.xml
+++ b/man/systemd.scope.xml
@@ -54,25 +54,20 @@ along with systemd; If not, see .
Description
- A unit configuration file whose name ends in
- .scope encodes information about a unit created
- by systemd to encapsulate processes not launched by systemd
- itself. This management is performed by creating a node in the
- control group tree. Processes are moved into the scope by means
- of the DBus API.
- systemd-run can be
- used to easily launch a command in a new scope unit.
-
- See
- systemd.unit5
- for the common options of all unit configuration
- files. The common configuration items are configured
- in the generic [Unit] and [Install] sections. The
- scope specific configuration options are configured in
- the [Scope] section. Currently, only generic cgroup settings
- as described in
- systemd.cgroup7 are allowed.
-
+ 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 may
+ be used to easily launch a command in a new scope unit from the
+ command line.Unless DefaultDependencies=false
is used, scope units will implicitly have dependencies of