summaryrefslogtreecommitdiff
path: root/debian/apt.cron.daily
diff options
context:
space:
mode:
authorMichael Vogt <michael.vogt@ubuntu.com>2008-05-05 11:21:13 +0200
committerMichael Vogt <michael.vogt@ubuntu.com>2008-05-05 11:21:13 +0200
commita2ec4d22dd77a363cd5b1f8b55ed34ba88331396 (patch)
tree1f4995e44a20923ecc69c3ed30ec788d38b81b49 /debian/apt.cron.daily
parent5c92e3800d6ce8e9cde1e2816bd76c975d9342a7 (diff)
parent549da1a850f0fd50e0a55415452ecaa735d49451 (diff)
merged from debian
Diffstat (limited to 'debian/apt.cron.daily')
-rw-r--r--debian/apt.cron.daily11
1 files changed, 10 insertions, 1 deletions
diff --git a/debian/apt.cron.daily b/debian/apt.cron.daily
index 2f1a59744..a5c646d92 100644
--- a/debian/apt.cron.daily
+++ b/debian/apt.cron.daily
@@ -193,8 +193,17 @@ if which on_ac_power >/dev/null; then
fi
# check if we can lock the cache and if the cache is clean
+# There's a reasonable chance that someone is already running an apt
+# frontend that has locked the cache, so exit quietly if it is locked.
+if ! apt-get check -q -q 2>/dev/null; then
+ exit 0
+fi
+
+# sleep random amount of time
+random_sleep
+
+# check again if we can access the cache
if ! apt-get check -q -q 2>/dev/null; then
- echo "$0: could not lock the APT cache"
exit 1
fi