Re: crond, hwclock, and clockspeed

[email protected] (Paul Jarc) writes:

> Lloyd Zusman <[email protected]> wrote:
>> I'm guessing that this is just some sort of idiosyncracy of Linux's
>> crond.  Perhaps it tries to be smart about leap seconds itself, thereby
>> getting confused by the right/leapsecs.dat stuff ... ???
>
> I would guess that it does date arithmetic by essentially
> reimplementing libc's localtime(), and assuming a POSIX clock.  Other
> schedulers may not have the same problem.  At least, mine doesn't. :)

Yes, I took a look at "runwhen" just today, actually.  I presume that's
what you're referring to. :)

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?
If I had a utility like that, I'd switch to runwhen in a heartbeat.

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.

If such a tool doesn't already exist, I guess I'll just have to write it
myself ... which I'll be glad to do.


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