Package: cron-apt
Version: 0.4.9
Severity: normal
Hi,
on systems with a long sources.list, servers unreachable and cron-apt
being invoked often, it is possible that a new cron-apt is started
while the old one is still running. In this case, the new cron-apt
terminates with a message that it cannot acquire the cron-apt log. So
far, so good.
At this time, $TMPDIR/initlog was already created, but onexit()
doesn't zap $TMPDIR/initlog, and thus the rmdir $TMPDIR in onexit()
fails ("Directory not empty"). This error message is delivered by cron
in an extra mail message.
Greetings
Marc
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.3-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages cron-apt depends on:
ii apt 0.6.46.3 Advanced front-end for dpkg
ii debianutils 2.17.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]
