On Wed, 13 Jan 2016, Bernardo J Mora wrote:
So I’ve never been fussy about hitting the top of hour IDs exactly, but
usually they’re within a minute or two…
Except at midnight. During the week I tend to run two longer programs in
the 11PM hour, the first of which may run longer than 1/2 hour, and the
second timed at exactly 29 minutes. But I would expect my midnight legal
ID (next day’s log), scheduled “timed, make next” at 00:00 to be the
next event after midnight, even if it’s a few minutes after…
I've learned the hard way to be very careful with putting timed events
anywhere near midnight.
You could put an ID just before midnight (say, 23:59:50) as a timed event
set "start immediately", followed by the log chain. That will run your ID
on time and start tomorrow's log, but at the expense of blowing away
whatever remains of your 11 PM program.
The other way to do it is to set the ID up as a timed event an an aux log,
followed by a chain t the same log. The ID will then play on top of the
program running in the main log, which will then continue to run.
Rob
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
