Adding to Lorne's comment, I have always avoided using the exact TOH as an event time on time-change night and have never had any trouble in 5 years of running Rivendell. Also, just adding a report that an event for 03:00:13 last night, executed perfectly.
But if you are meeting the network straight up, that might pose a problem. Perhaps a possible couple second upcut twice a year in the dead of night is acceptable? --Chuck W. On Sun Mar 10 13:22:03 EDT 2019 Lorne Tyndale ltyndale at tyndaleweb.com wrote: > If the clock is correct and changes as it should then this should > work. > However if for some reason the clock doesn't change, or if you're in > a networked environment where all the rivendell workstation clocks > are not sync'ed with the server, then I've run into issues - not > related to time change, but related to when a workstation triggers > an event versus the time the server has (particularly with rdcatch). > > One option is to schedule the event for 1 to 2 seconds after the TOH, > I've found that smooths out the RDCatch issues that I see > occasionally. I imagine it should work for time change too. > > Lorne Tyndale On Sun, 10 Mar 2019 07:39:22 -0400 (EDT) Rob Landry <[email protected]> wrote: > > One of my clients had a timed event scheduled for 3:00 AM this > > morning, that is, for the instant that 2 AM suddenly becomes 3 AM, > > and the event did not fire. > > > > Does anyone know if this feature has ever been tested under these > > conditions? > > > > > > Rob _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
