If the system time on a host changes during a "sleep period", NCron will
not notice the change until the next job is picked up for execution. In an
installation where jobs are executed infrequently (hours/days/weeks in
between), this might cause jobs to be missed when system time is changed
radically (switching to/from DST).
Unix cron engines tend to wake up periodically (even every minute) to
recompute distances to next job execution. NCron should have similar
behavior, while balancing risk of missing a job with performance.
Original issue reported on code.google.com by jsr%mala...@gtempaccount.com on 7 Jan 2010 at 5:28
Original issue reported on code.google.com by
jsr%mala...@gtempaccount.com
on 7 Jan 2010 at 5:28