From 9365b048c0c9f62ef7f696216ba049e6b4c2f2e5 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 19 Jul 2013 19:04:17 +0200 Subject: man: update scope unit man page a bit --- man/systemd.cgroup.xml | 6 +++++- man/systemd.scope.xml | 33 ++++++++++++++------------------- man/systemd.snapshot.xml | 2 +- 3 files changed, 20 insertions(+), 21 deletions(-) (limited to 'man') diff --git a/man/systemd.cgroup.xml b/man/systemd.cgroup.xml index c2a823eba5..12b19f5c4b 100644 --- a/man/systemd.cgroup.xml +++ b/man/systemd.cgroup.xml @@ -44,7 +44,7 @@ along with systemd; If not, see . systemd.cgroup - Cgroup configuration unit settings + Control Group configuration unit settings @@ -66,6 +66,10 @@ along with systemd; If not, see . configuration options which configure the control group settings for spawned processes. + Control Groups is a concept for organizing processes in a + hierarch tree of named groups for the purpose of resource + management. + This man page lists the configuration options shared by those six unit types. See systemd.unit5 diff --git a/man/systemd.scope.xml b/man/systemd.scope.xml index 126440a15f..1400f8f4b1 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 D-Bus 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 resource management. + + 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 diff --git a/man/systemd.snapshot.xml b/man/systemd.snapshot.xml index 4e8d5a901f..1bb074a9b1 100644 --- a/man/systemd.snapshot.xml +++ b/man/systemd.snapshot.xml @@ -56,7 +56,7 @@ Snapshot units are not configured via unit configuration files. Nonetheless they are named - similar to filenames. A unit name whose name ends in + similar to filenames. A unit whose name ends in .snapshot refers to a dynamic snapshot of the systemd runtime state. -- cgit v1.2.3-54-g00ecf