Don't use sudo -v, which was having issues (hanging bots).

Change-Id: I5f76f0f27b5789d88740b36fa6ce696ef7e68e8a

BUG=chromium-os:11602
TEST=Tried steps in bug 11602 (but hacked a sudo -K to the start of teardown_env so I didn't need to wait 15 mins).

Review URL: http://codereview.chromium.org/6286069
This commit is contained in:
Doug Anderson 2011-02-02 16:10:34 -08:00
parent fd135cd9d0
commit 3d7fa3a0e9

View File

@ -127,7 +127,8 @@ LOCKFILE="$FLAGS_chroot/var/lock/enter_chroot"
function setup_env { function setup_env {
# Validate sudo timestamp before entering the critical section so that we # Validate sudo timestamp before entering the critical section so that we
# don't stall for a password while we have the lockfile. # don't stall for a password while we have the lockfile.
sudo -v # Don't use sudo -v since that has issues on machines w/ no password.
sudo echo "" > /dev/null
( (
flock 200 flock 200
@ -238,7 +239,8 @@ function setup_env {
function teardown_env { function teardown_env {
# Validate sudo timestamp before entering the critical section so that we # Validate sudo timestamp before entering the critical section so that we
# don't stall for a password while we have the lockfile. # don't stall for a password while we have the lockfile.
sudo -v # Don't use sudo -v since that has issues on machines w/ no password.
sudo echo "" > /dev/null
# Only teardown if we're the last enter_chroot to die # Only teardown if we're the last enter_chroot to die
( (