… or, “Hey, let’s start a flame war!”
Jason Kottke posted a little tidbit that the Linux evangelist in me will simple not leave lie:
If you had a job scheduled to run between 2AM and 3AM Sunday morning on a Windows server, and you observe Daylight Savings Time, it didn’t run. If you had a cron job scheduled on your Linux box, it ran at 3AM.
Now, both of these approaches have pluses and minuses. You could argue that, since 2:30 never happened, a job scheduled for that time shouldn’t run. Also, if you had dependent jobs (DL logs from server at 2:10, kick off stats parser at 2:40), something probably got monkeyed up.
Still, for 95% of all cases, the Linux approach is probably the best in this case. You’re running things at that hour because you don’t want to do them during the daytime, not because you have to run them at an exact time. And, if you’re writing time-dependent cron jobs, you’ve probably already had trouble without the help of Daylight Savings.
So, points for Linux. I just imagine a bunch of Windows sysadmins reading this right now thinking, “Oh man, what runs between two and three?!”