[7859] in athena10
Re: [Debathena] #968: Subsequent reboots after entering recovery
daemon@ATHENA.MIT.EDU (Debathena Trac)
Wed Jul 13 18:05:13 2011
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: jdreed@mit.edu, geofft@mit.edu
Date: Wed, 13 Jul 2011 22:05:04 -0000
Reply-To:
Message-ID: <052.17fa12ea83d950df18ff443d78b76eb5@mit.edu>
In-Reply-To: <043.3126ff6911d21c2b49483b571d0772bc@mit.edu>
Content-Transfer-Encoding: 8bit
#968: Subsequent reboots after entering recovery mode will sit at the grub menu
forever---------------------+------------------------------------------------------
Reporter: jdreed | Owner:
Type: defect | Status: new
Priority: blocker | Milestone: Natty Release
Component: -- | Keywords:
See_also: |
---------------------+------------------------------------------------------
Comment(by geofft):
This is from /etc/grub.d/00_header:
{{{
cat << EOF
if [ \${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=${GRUB_TIMEOUT}
fi
EOF
}}}
The easiest way to set another timeout is to drop a later .d script that
prints a different "set timeout" line. For -cluster, unconditionally using
$GRUB_TIMEOUT is fine. For -workstation or below, I'm uncomfortable
messing with GRUB, but if we have to, copying the code in a later .d
script using something like 300 instead of -1 would at least let the
machine boot unattended. (But usually if you're going to the recovery menu
and not exiting the recovery menu by booting cleanly, it's because the
machine won't boot normally and needs manual attention, so this behavior
is reasonable.)
Depending on what you want to do here, e.g. a recovery menu item that
automatically reboots, running `grub-editenv /boot/grub/grubenv unset
recordfail` (cf. /etc/pm/sleep.d/10_grub-common) just before rebooting
would also work.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/968#comment:1>Debathena <http://debathena.mit.edu/>MIT Debathena Project
