tickless cron

[Rogelio Serrano]

On 9/3/06, Rob Landley <rob at landley.net> wrote:
> >
> > yes thats right. so these epochs are placed in a priority queue. then
> > a timer, like select, is programmed by the difference between the
> > current time and next epoch.
>
> You only ever care about the _next_ wakeup.
>
> The stupid way to do this with almost no changes to the existing code is with
> a for loop over the next 24 hours checking every 1 minute interval in the
> future via the existing logic until you get a hit.  This eats CPU to do the
> calculation, but 60*24 is only 1440 which isn't that bad, and it then lets
> you power down the processor for longer.  If you don't find an event within
> the next 24 hours, set 24 hours from now as the timeout point and try again
> when you wake up.  (This catches "every sunday" style events.  You still wake
> up once a day.  Big deal.)
>

i considered that already. i dont like it.

so it looks like there is no cron compatible sched string way to do this.

> Rob
> --
> Never bet against the cheap plastic solution.
>


-- 
things i hate about my linux pc:

1. it takes more than a second to boot up
2. keeps asking about filenames and directories
3. does not remember what i was working on yesterday
4. does not remember all the changes i have ever made
5.cannot figure out necessary settings by itself