Re: crond, hwclock, and clockspeed

[email protected] (Paul Jarc) writes:

> Lloyd Zusman <[email protected]> wrote:
>> Yes, I took a look at "runwhen" just today, actually.  I presume that's
>> what you're referring to. :)
>
> Yep.
>
>> Do you or anyone else here have a tool that will automatically generate
>> runwhen scripts based on syntax that's at least vaguely crontab-like?
>
> http://code.dogmap.org./runwhen/#related
>
>> I schedule a few once-a-month jobs, and therefore, this desired utility
>> would also have to generate runwhen scripts that manage programs that
>> run on more-than-25-day intervals on my 2.6 linux system.
>
> One way to handle that would be to have your script sleep for, say, a
> constant two weeks ("rw-add n d14d wake rw-sleep \$wake ..."), and
> then from there figure out how long it is until the next run time and
> sleep again.  Early wakeups with "svc -a" would require some special
> handling.

Thanks.  I overlooked the "migration tool" link the first time around.

Hmm ... couldn't the >25-day case be handled by rw-sleep, which could
break long intervals into a group of slightly-less-than-25-day
increments?  This could be enabled via conditional compilation for those
of us who have broken^H^H^H^H^H^Hmodern linux setitimer calls, with
the current functionality being the default for everyone else.

Or am I missing something?


-- 
 Lloyd Zusman
 [email protected]
 God bless you.