[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#479800: marked as done (exit BEFORE random_sleep() in cron script)



Your message dated Tue, 07 Oct 2008 08:27:33 +0200
with message-id <87zllgex7u.fsf@gmx.de>
and subject line Re: Bug#479141: apt: cron.daily script delays other cron tasks
has caused the Debian Bug report #479141,
regarding exit BEFORE random_sleep() in cron script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
479141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479141
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.7.12
File: /etc/cron.daily/apt

Please have /etc/cron.daily/apt check its variables and realize if it
has any work to do and if not EXIT BEFORE waiting around the
random_sleep()!

The user might not have the *luxury* of turning his computer on for
how long you *assume* he will.

Indeed, please FIRST check all the variables, and if all are 0, please
exit before even loading all those bash functions.

First task before all others: Are we to do any work at all? If no then
exit as early in the script as possible.

E.g., "a quick addition of the variables gives zero, exiting here".



--- End Message ---
--- Begin Message ---
Package: apt
Version: 0.7.15

On 2008-05-03 07:49 +0200, Sven Joachim wrote:

> In the last few days I was wondering whether my system was
> broken. Saw messages like that in xconsole:
>
> ,----
> | May  3 06:40:19 debian anacron[2600]: Job `cron.daily' started
> | May  3 06:40:19 debian anacron[2745]: Updated timestamp for job `cron.daily' to 2008-05-03
> `----
>
> and then nothing happened for quite some time.  You probably can figure
> out more easily than me why that is the case, it would be nice if your
> cron.daily script could check whether it should do anything *before*
> sleeping up to 30 minutes and holding up everyone else.

This is fixed in apt 0.7.15.  Maybe it was already in 0.7.14, but only
yesterday I accepted the new /etc/cron.daily/apt conffile (had put an
"exit 0" at the top of it before).  Today's cron job for apt took only
one second, so the bug can be closed.

Sven


--- End Message ---

Reply to: