Add support for GRUB_RECORDFAIL_TIMEOUT option #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GRUB2 includes a RECORDFAIL feature which means that the boot after a failed boot
will always stop at the boot menu. We can set a timeout value to stop headless systems
failing at this point. There is a difference between the TIMEOUT and RECORDFAIL_TIMEOUT
features, as the former will occur on all boots; the latter occurs only on the boot after a failed boot.
The GRUB_RECORDFAIL_TIMEOUT option allows users to set a default timeout
value to occur should a system running GRUB2 not receive any input at all at
a prompt. If the timeout value is reached, the system continues to boot
using whatever the first or otherwise selected option is. This is a
particularly useful setting on headless systems where stalling boots can cause
pain.
GRUB_RECORDFAIL_TIMEOUT takes an integer as it's value, which is the time in
seconds to wait before timing out and continuing the boot sequence.
This commit: