I think there is a difference between having to figure something out and actually being told what the problem is. If you're told what the problem is, it shouldnt take but maybe 1-2 minutes to fix (which was the case here). See, in a previous thread I had flat out told iL that it was very likely a cron job causing the problem. Do you know what his response to that was? He specifically said he had eliminated that as a possible cause. So I took his word for it and then the next obvious cause was the host itself. But now, weeks later, we're finding out that it was indeed my very first suggestion of a cronjob being the issue. How do you fix that? Here, I'll show you.
Below is the bad cronjob
0 21 * * * Do Something here
And here is the fix.
#0 21 * * * Do something here
Now tell me in what world would that fix take days, weeks, hours, hell even minutes? Now maybe you'll see where my disappointment comes from. Because it really is THAT simple to stop a cronjob from starting. Simply comment it out. Done. Then in spare time, try to figure out WHY cronjob was misbehaving. Changing the time it runs is not the answer. Completely disabling it IS the answer.
