Package: cron-apt
Version: 0.4.5
Severity: minor
Hi,
I am running cron-apt on an hourly basis. This might lead to the
following situation:
Prerequisite: One of the apt servers is down causing apt-get update to
take a _loooong_ time.
nn:00 cron-apt is started by cron, sleep time 3540 seconds
nn:59 apt-get update starts, stalls due to the apt server being down
nn+1:00 cron-apt is started by cron, sleep time 120 seconds
nn+1:02 apt-get update starts, reports "can't obtain apt lock" due to
the still running apt from the last round
This happens surprisingly often and increases the number of e-mails
generated since the "can't obtain apt lock" error message completely
messes up diff handling.
cron-apt should be changed to do the following
sleep
take out a lock
check if lock successful
if lock successful, continue
if lock unsuccessful, terminate with a log message, but not messing up
the diffs
Greetings
Marc
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages cron-apt depends on:
ii apt 0.6.43.3 Advanced front-end for dpkg
ii debianutils 2.15.3 Miscellaneous utilities specific t
Versions of packages cron-apt recommends:
ii liblockfile1 1.06.1 NFS-safe locking library, includes
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
