From: Lennart Poettering Date: Mon, 25 Jun 2018 15:21:34 +0000 (+0200) Subject: man: document new "boot-complete.target" unit X-Git-Tag: v240~500^2~12 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=82ea38258c0f4964c2f3ad3691c6e4554c4f0bb0;p=thirdparty%2Fsystemd.git man: document new "boot-complete.target" unit --- diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 0d25e40d03a..fd5639ba03e 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, @@ -144,7 +145,28 @@ bootup7 for details on the targets involved. + + + + 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.