On Thu, Mar 17, 2016 at 9:56 PM, Mike Carroll <[email protected]> wrote: > We had an issue with an RDCatch event over the weekend when the US time > changed: The event was scheduled at 5AM but ran at 6AM. Another event, > scheduled for 7AM, ran on time. > > Based on these two occurrences, I'm thinking RDCatch is using an interval > timer to wait for the next event in its list of things to do.
The fact that your 7:00 event occurred on time is strange. I'd go digging through the appropriate logs to see what the RDCatch daemon was doing, and also look at your system logs (e.g. /var/log/messages) to see when the time actually changed to DST. It almost sounds like your computer's TZ setting is set to Hawaiian time (5 hours behind ET) or Alaskan time (4 hours behind ET). I'd start by looking at your computer's TZ (timezone) setting to see if it's set to observe DST or not, and if it's set to the correct time zone. I'm not in front of a Linux machine at the moment, so I'm sorry for not giving you a definite "how-to" on the steps to check this, but it should be a quick 'Net search for such details. IIRC, you should see something like EST5EDT for the timezone if you're in Eastern Time and you observe daylight savings time. You might also want to find out if your computer uses UTC instead of local time for its BIOS clock. See 'man hwclock' for details. >From my work with it a number of years ago, I seem to recall that RDCatch looks at absolute time, not intervals. You can look at the mySQL tables to see the hard times for each RDCatch event. --Sherrod _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
