diff options
author | Lennart Poettering <lennart@poettering.net> | 2014-08-22 16:36:38 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2014-08-22 18:10:31 +0200 |
commit | 2928b0a863091f8f291fddb168988711afd389ef (patch) | |
tree | 10a0fad387c664a00b3ca173de9b521a91696eb7 /man/systemd.service.xml | |
parent | 2de1851fe3611c59abf77127c6b5bc1b91eb7cba (diff) |
core: add support for a configurable system-wide start-up timeout
When this system-wide start-up timeout is hit we execute one of the
failure actions already implemented for services that fail.
This should not only be useful on embedded devices, but also on laptops
which have the power-button reachable when the lid is closed. This
devices, when in a backpack might get powered on by accident due to the
easily reachable power button. We want to make sure that the system
turns itself off if it starts up due this after a while.
When the system manages to fully start-up logind will suspend the
machine by default if the lid is closed. However, in some cases we don't
even get as far as logind, and the boot hangs much earlier, for example
because we ask for a LUKS password that nobody ever enters.
Yeah, this is a real-life problem on my Yoga 13, which has one of those
easily accessible power buttons, even if the device is closed.
Diffstat (limited to 'man/systemd.service.xml')
-rw-r--r-- | man/systemd.service.xml | 23 |
1 files changed, 12 insertions, 11 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index e584a1f006..20d2a0d755 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1155,29 +1155,30 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}</programlisting> </varlistentry> <varlistentry> + <term><varname>FailureAction=</varname></term> + <listitem><para>Configure the action + to take when the service enters a failed + state. Takes the same values as + <varname>StartLimitAction=</varname> + and executes the same actions. + Defaults to <option>none</option>. + </para></listitem> + </varlistentry> + + <varlistentry> <term><varname>RebootArgument=</varname></term> <listitem><para>Configure the optional argument for the <citerefentry><refentrytitle>reboot</refentrytitle><manvolnum>2</manvolnum></citerefentry> system call if <varname>StartLimitAction=</varname> + or <varname>FailureAction=</varname> is a reboot action. This works just like the optional argument to <command>systemctl reboot</command> command.</para></listitem> </varlistentry> - <varlistentry> - <term><varname>FailureAction=</varname></term> - <listitem><para>Configure the action - to take when the service enters a failed - state. Takes the same values as - <varname>StartLimitAction=</varname> - and executes the same actions. - Defaults to <option>none</option>. - </para></listitem> - </varlistentry> - </variablelist> <para>Check |