54 lines
2.6 KiB
Diff
54 lines
2.6 KiB
Diff
|
From 8ad89170001c9aba8849630ddb5da81d9e24a1bc Mon Sep 17 00:00:00 2001
|
||
|
|
From: Lennart Poettering <lennart@poettering.net>
|
||
|
|
Date: Mon, 25 Jun 2018 17:21:34 +0200
|
||
|
|
Subject: [PATCH] man: document new "boot-complete.target" unit
|
||
|
|
|
||
|
|
(cherry picked from commit 82ea38258c0f4964c2f3ad3691c6e4554c4f0bb0)
|
||
|
|
|
||
|
|
Related: #1872243
|
||
|
|
---
|
||
|
|
man/systemd.special.xml | 23 +++++++++++++++++++++++
|
||
|
|
1 file changed, 23 insertions(+)
|
||
|
|
|
||
|
|
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
|
||
|
|
index fb12805fff..c9d4345016 100644
|
||
|
|
--- a/man/systemd.special.xml
|
||
|
|
+++ b/man/systemd.special.xml
|
||
|
|
@@ -29,6 +29,7 @@
|
||
|
|
<filename>cryptsetup-pre.target</filename>,
|
||
|
|
<filename>cryptsetup.target</filename>,
|
||
|
|
<filename>ctrl-alt-del.target</filename>,
|
||
|
|
+ <filename>boot-complete.target</filename>,
|
||
|
|
<filename>default.target</filename>,
|
||
|
|
<filename>emergency.target</filename>,
|
||
|
|
<filename>exit.target</filename>,
|
||
|
|
@@ -646,6 +647,28 @@
|
||
|
|
</para>
|
||
|
|
</listitem>
|
||
|
|
</varlistentry>
|
||
|
|
+ <varlistentry>
|
||
|
|
+ <term><filename>boot-complete.target</filename></term>
|
||
|
|
+ <listitem>
|
||
|
|
+ <para>This target is intended as generic synchronization point for services that shall determine or act on
|
||
|
|
+ whether the boot process completed successfully. Order units that are required to succeed for a boot process
|
||
|
|
+ to be considered successful before this unit, and add a <varname>Requires=</varname> dependency from the
|
||
|
|
+ target unit to them. Order units that shall only run when the boot process is considered successful after the
|
||
|
|
+ target unit and pull in the target from it, also with <varname>Requires=</varname>. Note that by default this
|
||
|
|
+ target unit is not part of the initial boot transaction, but is supposed to be pulled in only if required by
|
||
|
|
+ units that want to run only on successful boots.</para>
|
||
|
|
+
|
||
|
|
+ <para>See
|
||
|
|
+ <citerefentry><refentrytitle>systemd-boot-check-no-failures.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
||
|
|
+ for a service that implements a generic system health check and orders itself before
|
||
|
|
+ <filename>boot-complete.target</filename>.</para>
|
||
|
|
+
|
||
|
|
+ <para>See
|
||
|
|
+ <citerefentry><refentrytitle>systemd-bless-boot.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
||
|
|
+ for a service that propagates boot success information to the boot loader, and orders itself after
|
||
|
|
+ <filename>boot-complete.target</filename>.</para>
|
||
|
|
+ </listitem>
|
||
|
|
+ </varlistentry>
|
||
|
|
<varlistentry>
|
||
|
|
<term><filename>syslog.socket</filename></term>
|
||
|
|
<listitem>
|