Bug#459344: closed by Otavio Salvador <otavio@debian.org> (Bug#459344: fixed in apt 0.7.13)
Goswin von Brederlow <goswin-v-b@web.de> writes:
> Otavio Salvador <otavio@debian.org> writes:
>
>> Francesco Poli <frx@firenze.linux.it> writes:
>>
>>> On Fri, 02 May 2008 19:45:05 +0000 Debian Bug Tracking System wrote:
>>>
>>> [...]
>>>> * Make cron script quiet if cache is locked. Thanks to Ted Percival
>>>> <ted@midg3t.net> for the patch. Closes: #459344
>>>
>>> I don't quite agree with the way this patch is supposed to fix the
>>> issue.
>>>
>>> If /etc/cron.daily/apt has something to do on the system (because APT
>>> was configured accordingly), then, when the cache cannot be
>>> locked, /etc/cron.daily/apt cannot do its job and it should indeed exit
>>> *with errors* to alert the administrator that something went wrong!
>
> Does it at least wait a while? It is a daily jobs and if it runs an
> hour late because the cache was locked nobody will mind. An error mail
> just because apt-get was in use at the time cron.daily triggered is
> anoying though.
It makes sense to retry it, maybe 30min later again, and then if it
still fails, output an error?
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Reply to: