On 11/06/2012 06:24 AM, Michael George wrote:
> On Sun, Nov 04, 2012 at 06:36:50PM -0500, Michael Orlitzky wrote:
>> On 11/04/2012 03:16 PM, Michael George wrote:
>>> Local time changes of less than three hours, such as those
>>> caused by the start or end of Daylight Saving Time, are handled
>>> specially. This only applies to jobs that run at a specific
>>> time and jobs that are run with a granularity greater than one
>>> hour. Jobs that run more frequently are scheduled normally.
>>>
>>> ...
>>>
>>> So it seems that DST changes are accommodated. Is there some
>>> side-effect of the cron.<period> method of scheduling tasks that I'm
>>> overlooking?
>>>
>>
>> The run-crons script is triggered every ten minutes, and so avoids the
>> special handling. But the script is broken, and has been so forever:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=69777
>
> I'm surprised that hasn't been fixed by now. Looking at the cron guide
> (https://bugs.gentoo.org/show_bug.cgi?id=69777), is bcron subject to the
> same problem because the run-crons script is in cronbase and not part of
> the cron daemon?
>
I think all of them are, out-of-the-box. I just commented on the bug. I
think the sensible thing to do is delete the time-management code in the
run-crons script. It's only there as a half-assed attempt to run your
missed jobs after a reboot, which fcron (and maybe others) does properly.
If you don't want to mess with run-crons, you could just replace the
stuff in /etc/crontab. All you really need is one command per line that
does (untested),
find "/etc/cron.${PERIOD}" -type f -executable -exec bash '{}' \;
