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 strai
On Mar 10, 2019, at 14:14, al davis wrote:
>
> Not a surprise ... For that instant, the time is 2 AM, but one second
> later it's 3:00:01. The exact time of 3 AM does not exist. It's just
> like 2:30 AM.
Not quite. In the United States, the forward transition looks like this:
[…]
01:59:58
01:
On Sun, 10 Mar 2019 07:39:22 -0400 (EDT)
Rob Landry <41001...@interpring.com> 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.
Not a surprise ... For that instant, the time i
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, b
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
--
Я там, где ребята толковые,
Я там, где плакат
