Mailinglist Archive: opensuse-bugs (14787 mails)

< Previous Next >
[Bug 221999] cron.daily not running daily
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 17 Nov 2006 07:20:58 -0700 (MST)
  • Message-id: <20061117142058.CC44425C887@xxxxxxxxxxxxxxxxxxxxxx>

mkoenig@xxxxxxxxxx changed:

What |Removed |Added
Info Provider|ke@xxxxxxxxxx |
Resolution| |INVALID

------- Comment #3 from mkoenig@xxxxxxxxxx 2006-11-17 07:20 MST -------
Note, that MAX_NOT_RUN is only used, if and only if DAILY_TIME has been set.
DAILY_TIME is still "" in default configuration, so I do not see any problem.

This has been introduced to run the cron.daily scripts at a specific time at
the day (instead of 15 minutes after boot time). MAX_NOT_RUN has been
introduced only for the case if the machine is not running, we may miss that
time when cron.daily is supposed to run.
This may happen for several days, but after 5 days we force the run of
cron.daily scripts *even* if the time specified in DAILY_TIME is not current

Of course this should be documented, but I don't consider this as a bug.
The feature has been introduced to resolve #114761.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >