Re: crond, hwclock, and clockspeed

Thorsten Glaser <[email protected]> writes:

> Lloyd Zusman dixit:
>
>>I'm guessing that this is just some sort of idiosyncracy of Linux's
>
> This is MirBSD, not GNU/Linux, here, and our cron also has this behaviour.
> (MirBSD only has "right" timezones, no "POSIX" ones.)
>
>>crond.  Perhaps it tries to be smart about leap seconds itself, thereby
>>getting confused by the right/leapsecs.dat stuff ... ???
>
> I can't explain the 39 then. If it were 22, I'd agree. If it were -22
> (or 38), I'd agree.

Well, sometimes cron jobs start running one second late, depending on
where within the span of a second the daemon wakes up, how long it takes
to fork processes, etc.  Therefore, perhaps *:*:39 is the same as
*:*:01.  I have less than a day of log entries, and so I don't know if
after a while, some of them might end up being *:*:38.  I do see a
number of these *:*:01 entries within cron logs for daemons not running
under right/leapsecs.dat.


> //mirabile

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