Re: [9fans] *poof*

["Steve Simon" <steve@quintile.net>]

> I had the same problem with ddr.9grid.de. It ran out of memory short
> after cron was started. For now cron is turned off there, but that is
> no real solution.

I too had problems with cron, It seemed that timesync can
set the current time back a long way (days) in some circumstances
and when it discovers its error and corrects the system clock
cron goes nuts trying to run all the jobs that have been missed.
This only happened once a month, and somtimes at system boot so
it was difficult to debug. I looked at timesync but it looked
correct to me.

I submitted a patch to cron which should have prevented the madness
(only 24 hours of catchup performed at most), and though it helped,
it didn't seem to cover all cases.

I have now I delayed the start of cron until timesync has (hopefully)
stabalised the system clock, which seems to solved the problem.

	felix% grep cron /rc/bin/cpurc
	{ sleep 600; auth/cron >> /sys/log/cron } &

not really a solution, more of a workaround.

-Steve