there are two solutions 1 make sure you overschedule that last hour clock. 2 figure out how an event at the end of the log [chainto] is being called at midnight. Have you got a time sync just before it?
Put the time sync at 11:55 then schedule close to 5 minutes and let the chainto event happen somewhere around midnight. You can ratchet it tighter but you have to build around the changeover and the first events in the 00 clock need to be long enough to get over the running time vs wall time contest. Robert On 19/10/2011 20:47, Benjamin D. Fillmore wrote: > We are experiencing a random but recurring problem. Sometimes the > chain-to event will happen slightly before midnight. The problem is > that when this happens, the next log loads, and then at midnight, the > log forces the NEXT chain-to event to trigger which either puts us on > the wrong day's log, or halts the system (if there isn't a log for the > next day in the system yet). > > It happens multiple times a week. We are having to log in to the system > remotely after midnight EVERY day just to make sure the station is still > on-air. Obviously, not the ideal situation. > > I believe there must be a reliable fix, or else this system would not be > so widely used. > > Looking forward to for an answer to this dilemma.... > > Thank you! > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev -- Robert Jeffares Big Valley Radio Thames New Zealand _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
