daandemeyer / rpms / systemd

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