Since most of my servers are Unix based I just use CRON and cURL to run a scheduled task. Here is what Cron Does...
"Suppose I have a job scheduled to run at 2:15 Sunday morning. When we "spring ahead", there won't be a 2:15. cron will note that we "sprung ahead" by 60 minutes, so it will add 60 minutes to my job time getting 3:15. It will run the job at 3:15...unless the job was already scheduled to run at both 2:15 and 3:15. In that case, my job will run once at 3:15. Later in the year, we "fall back". On that Sunday, it will be 2:15 twice. My job will only run at the first 2:15. If my job is scheduled to run at 15 minutes after every hour via the explicit use of an asterisk in the hour field my job will run at both 2:15's. This is not true if I use a range or a list of hours to run. Only jobs with an asterisk for the hour field run at both 2:15's." from http://www.unix.com/tips-tutorials/35535-understanding-unix-timekeeping.html (3rd post) Seems to me that the scheduled task engine could work the same way but it would be nice to get a clarification. -J.J. On Tue, Mar 13, 2012 at 1:45 PM, Leigh <[email protected]> wrote: > >> he was responsible for DST not timezones. > > That was my tired brain lumping all time related annoyances together. > >> DST was probably a good idea once but >> now its there to remind developers how cruel the world really is. > > The decision to change it, over several years, .. now that was cruel > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:350454 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
