X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.scope.xml;h=e047f4b7b405e32938337ff898baa518d313cae3;hp=1400f8f4b1ea942bccb27bdb059cc8d6ecb7aa40;hb=4cd1214db6cf4b262e8ce6381bc710091b375c96;hpb=9365b048c0c9f62ef7f696216ba049e6b4c2f2e5 diff --git a/man/systemd.scope.xml b/man/systemd.scope.xml index 1400f8f4b..e047f4b7b 100644 --- a/man/systemd.scope.xml +++ b/man/systemd.scope.xml @@ -58,17 +58,22 @@ along with systemd; If not, see . 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 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 resource management. + 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. + See the New + Control Group Interfaces for an introduction on how to make + use of scope units from programs. + Unless DefaultDependencies=false is used, scope units will implicitly have dependencies of type Conflicts= and @@ -86,7 +91,7 @@ along with systemd; If not, see . systemd1, systemd-run1, systemd.unit5, - systemd.cgroup5, + systemd.resource-control5, systemd.service5, systemd.directives7.