Mailinglist Archive: opensuse-bugs (8048 mails)

< Previous Next >
[Bug 243020] New: cron reloads config too late
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 7 Feb 2007 03:46:59 -0700 (MST)
  • Message-id: <bug-243020-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: cron reloads config too late
Product: SUSE Linux 10.1
Version: Final
Platform: Other
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: A.M.Iwi@xxxxxxxx
QAContact: qa@xxxxxxx

If you edit a crontab file so that a cron job will run during the following
minute, it does not run, because at the next minute the daemon will run jobs
scheduled for that minute that it already knew about, and only reread the
config after launching any jobs. e.g. if you edit crontab at 00:00:30, and add
a job to run at 00:01 then it won't run, although you can add a job to run at
00:02 and it will. This is a bit of a nuisance when testing cron jobs.

Looking at the source code, there is a call to load_database() at the end of
the infinite loop in main() in cron.c. I haven't tried it, but it seems
reasonably obvious that if that call was moved to just after the "while" loop
which has the comment "wait for the time (in minutes) to change", then it would
solve this problem.

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 >