diff options
author | Lennart Poettering <lennart@poettering.net> | 2018-06-26 15:14:57 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2018-10-19 22:34:50 +0200 |
commit | 04431cd1f8e1544ac6515ced821a6a7ff98f6909 (patch) | |
tree | a968197575588d978d12854d9800822801ea2d76 /man/systemd-boot-check-no-failures.service.xml | |
parent | ab3fc7b1935093fb63f476a06cbebc3f12cd9257 (diff) | |
download | systemd-04431cd1f8e1544ac6515ced821a6a7ff98f6909.tar.gz |
man: document systemd-boot-check-no-failures.service
Diffstat (limited to 'man/systemd-boot-check-no-failures.service.xml')
-rw-r--r-- | man/systemd-boot-check-no-failures.service.xml | 54 |
1 files changed, 54 insertions, 0 deletions
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 @@ +<?xml version='1.0'?> <!--*-nxml-*--> +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" + "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> + +<!-- + SPDX-License-Identifier: LGPL-2.1+ +--> + +<refentry id="systemd-boot-check-no-failures.service" + xmlns:xi="http://www.w3.org/2001/XInclude"> + + <refentryinfo> + <title>systemd-boot-check-no-failures.service</title> + <productname>systemd</productname> + </refentryinfo> + + <refmeta> + <refentrytitle>systemd-boot-check-no-failures.service</refentrytitle> + <manvolnum>8</manvolnum> + </refmeta> + + <refnamediv> + <refname>systemd-boot-check-no-failures.service</refname> + <refpurpose>verify that the system booted up cleanly</refpurpose> + </refnamediv> + + <refsynopsisdiv> + <para><filename>systemd-boot-check-no-failures.service</filename></para> + <para><filename>/usr/lib/systemd/system-boot-check-no-failures</filename></para> + </refsynopsisdiv> + + <refsect1> + <title>Description</title> + + <para><filename>systemd-boot-check-no-failures.service</filename> 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 + <filename>boot-complete.target</filename>, thus ensuring the target cannot be reached when the system booted up + with failed services.</para> + + <para>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 + <filename>boot-complete.target</filename>.</para> + </refsect1> + + <refsect1> + <title>See Also</title> + <para> + <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, + <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>1</manvolnum></citerefentry> + </para> + </refsect1> + +</refentry> |