dcavalca / rpms / systemd

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