|
Just to clarify and make certain I don't misunderstand, I would expect that a job scheduled for 2:30AM would run as soon after 3:00AM as CPU cycles would allow for the job scheduler. (Though Rob said 1:30 AM, I'd guess he meant 2:30AM.) That is, the scheduler wouldn't necessarily be running a job exactly, precisely at a given time. More likely, it would run the job starting at the time the signal arrived that indicated a scheduled time had passed. For 2:30AM on the morning of a time change from 2:00AM to 3:00AM, that signal _ought_ to be generated at 3:00AM. (Or 3:00:00.000001AM or whatever.) Make sense? It would depend on how the signal was generated (whatever the "signal" is). Tom Liotta midrange-l-request@xxxxxxxxxxxx wrote: > 8. RE: Daylight Saving Time (Bruce Vining) > > >Yes the job would run. > >Bruce Vining > > rob > RE: Daylight Saving Time > >Good news on the job scheduler not running the 1:30am job twice in the >fall, when you have two 1:30am's in one night. >Will it run it at all in the spring when you have no 1:30am? > >Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.