From 04431cd1f8e1544ac6515ced821a6a7ff98f6909 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 26 Jun 2018 15:14:57 +0200 Subject: [PATCH] man: document systemd-boot-check-no-failures.service --- man/rules/meson.build | 1 + ...systemd-boot-check-no-failures.service.xml | 54 +++++++++++++++++++ 2 files changed, 55 insertions(+) create mode 100644 man/systemd-boot-check-no-failures.service.xml diff --git a/man/rules/meson.build b/man/rules/meson.build index 93e410a5cb..4258bd0633 100644 --- a/man/rules/meson.build +++ b/man/rules/meson.build @@ -618,6 +618,7 @@ manpages = [ ['systemd-backlight@.service', '8', ['systemd-backlight'], 'ENABLE_BACKLIGHT'], ['systemd-binfmt.service', '8', ['systemd-binfmt'], 'ENABLE_BINFMT'], ['systemd-bless-boot.service', '8', [], 'ENABLE_EFI'], + ['systemd-boot-check-no-failures.service', '8', [], ''], ['systemd-boot', '7', ['sd-boot'], 'ENABLE_EFI'], ['systemd-cat', '1', [], ''], ['systemd-cgls', '1', [], ''], diff --git a/man/systemd-boot-check-no-failures.service.xml b/man/systemd-boot-check-no-failures.service.xml new file mode 100644 index 0000000000..55c2adffdb --- /dev/null +++ b/man/systemd-boot-check-no-failures.service.xml @@ -0,0 +1,54 @@ + + + + + + + + + systemd-boot-check-no-failures.service + systemd + + + + systemd-boot-check-no-failures.service + 8 + + + + systemd-boot-check-no-failures.service + verify that the system booted up cleanly + + + + systemd-boot-check-no-failures.service + /usr/lib/systemd/system-boot-check-no-failures + + + + Description + + systemd-boot-check-no-failures.service is a system service that checks whether the + system booted up successfully. This service implements a very minimal test only: whether there are any failed units on + the system. This service is disabled by default. When enabled, it is ordered before + boot-complete.target, thus ensuring the target cannot be reached when the system booted up + with failed services. + + Note that due the simple nature of this check this service is probably not suitable for deployment in most + scenarios. It is primarily useful only as example for developing more fine-grained checks to order before + boot-complete.target. + + + + See Also + + systemd1, + systemd.special1 + + + +