From 8ad89170001c9aba8849630ddb5da81d9e24a1bc Mon Sep 17 00:00:00 2001 From: Lennart Poettering 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 @@ cryptsetup-pre.target, cryptsetup.target, ctrl-alt-del.target, + boot-complete.target, default.target, emergency.target, exit.target, @@ -646,6 +647,28 @@ + + boot-complete.target + + 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 Requires= 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 Requires=. 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. + + See + systemd-boot-check-no-failures.service8 + for a service that implements a generic system health check and orders itself before + boot-complete.target. + + See + systemd-bless-boot.service8 + for a service that propagates boot success information to the boot loader, and orders itself after + boot-complete.target. + + syslog.socket