shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-02-02 13:47:27 +03:00
Code

man: list scope and slice units in systemd(1)

Browse Source
This commit is contained in:
Lennart Poettering 2013-07-19 18:44:33 +02:00
parent 60211b3507
commit 1ec96668dd
2 changed files with 33 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
TODO
View File

@ -46,7 +46,7 @@ CGroup Rework Completion:
* introduce high-level settings for RT budget, swappiness * introduce high-level settings for RT budget, swappiness
* wiki: document new bus APIs of PID 1 (transient units, Reloading signal) * wiki: document new bus APIs of PID 1 (transient units, Reloading signal)
* review: scope units, slice units, pid1, pam_system, systemctl commands * review: scope units, slice units, pam_system, systemctl commands
* Send SIGHUP and SIGTERM in session scopes * Send SIGHUP and SIGTERM in session scopes

50
man/systemd.xml
View File

@ -285,25 +285,27 @@
<title>Concepts</title> <title>Concepts</title>
<para>systemd provides a dependency system between <para>systemd provides a dependency system between
various entities called "units". Units encapsulate various entities called "units" of 12 different
various objects that are relevant for system boot-up types. Units encapsulate various objects that are
and maintenance. The majority of units are configured relevant for system boot-up and maintenance. The
in unit configuration files, whose syntax and basic majority of units are configured in unit configuration
set of options is described in files, whose syntax and basic set of options is
described in
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
however some are created automatically from other however some are created automatically from other
configuration or dynamically from system state. Units configuration, dynamically from system state or
may be 'active' (meaning started, bound, plugged in, programmatically at runtime. Units may be 'active'
... depending on the unit type, see below), or (meaning started, bound, plugged in, ... depending on
'inactive' (meaning stopped, unbound, unplugged, ...), the unit type, see below), or 'inactive' (meaning
as well as in the process of being activated or stopped, unbound, unplugged, ...), as well as in the
deactivated, i.e. between the two states (these states process of being activated or deactivated,
are called 'activating', 'deactivating'). A special i.e. between the two states (these states are called
'failed' state is available as well which is very 'activating', 'deactivating'). A special 'failed'
similar to 'inactive' and is entered when the service state is available as well which is very similar to
failed in some way (process returned error code on 'inactive' and is entered when the service failed in
exit, or crashed, or an operation timed out). If this some way (process returned error code on exit, or
state is entered the cause will be logged, for later crashed, or an operation timed out). If this state is
entered the cause will be logged, for later
reference. Note that the various unit types may have a reference. Note that the various unit types may have a
number of additional substates, which are mapped to number of additional substates, which are mapped to
the five generalized unit states described the five generalized unit states described
@ -312,7 +314,7 @@
<para>The following unit types are available:</para> <para>The following unit types are available:</para>
<orderedlist> <orderedlist>
<listitem><para>Service units, which control <listitem><para>Service units, which start and control
daemons and the processes they consist of. For daemons and the processes they consist of. For
details see details see
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem> <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
@ -369,6 +371,18 @@
objects change or are modified. See objects change or are modified. See
<citerefentry><refentrytitle>systemd.path</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem> <citerefentry><refentrytitle>systemd.path</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
<listitem><para>Slice units may be used to
group units which manage system processes
(such as service and scope units) in a
hierachial tree for resource management
purposes. See
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
<listitem><para>Scope units are similar to
service units, but manage foreign processes
instead of starting them as well. See
<citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
</orderedlist> </orderedlist>
<para>Units are named as their configuration <para>Units are named as their configuration