diff options
| author | Luca Boccassi <bluca@debian.org> | 2024-10-03 21:50:38 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2024-10-04 12:22:55 +0200 |
| commit | 3509fe124d3a4fe2934028f83ae156ade050c8fe (patch) | |
| tree | 17f87af185a56ccac7f39e2a89d1107900a918af /man/systemd.xml | |
| parent | Merge pull request #34610 from poettering/exec-start-single-line (diff) | |
| download | systemd-3509fe124d3a4fe2934028f83ae156ade050c8fe.tar.xz systemd-3509fe124d3a4fe2934028f83ae156ade050c8fe.zip | |
man: consolidate list of active unit states into a shared table
Avoids the need to maintain the same list over and over again, and
link it to the defition table in the implementation as a reminder
too
Diffstat (limited to 'man/systemd.xml')
| -rw-r--r-- | man/systemd.xml | 15 |
1 files changed, 5 insertions, 10 deletions
diff --git a/man/systemd.xml b/man/systemd.xml index af1681352e..71da1ec8f1 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -95,16 +95,11 @@ described in <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, however some are created automatically from other configuration files, dynamically from system state or - programmatically at runtime. Units may be "active" (meaning started, bound, plugged in, …, depending on - the unit type, see below), or "inactive" (meaning stopped, unbound, unplugged, …), as well as in the - process of being activated or deactivated, i.e. between the two states (these states are called - "activating", "deactivating"). A special "failed" state is available as well, which is very similar to - "inactive" and is entered when the service failed in some way (process returned error code on exit, or - crashed, an operation timed out, or after too many restarts). If this state is entered, the cause will - be logged, for later reference. Units may also be in a special transient state for a time, to indicate - that some operation is being performed on them, before reverting to the previous state, such as - "maintenance", "reloading" or "refreshing". Note that the various unit types may have a number of - additional substates, which are mapped to the five generalized unit states described here.</para> + programmatically at runtime. Units may be in a number of states, described in the following table. Note + that the various unit types may have a number of additional substates, which are mapped to the + generalized unit states described here.</para> + + <xi:include href="unit-states.xml" xpointer="table"/> <para>The following unit types are available:</para> |