I'm running Icecast 2.3.1 on a Windows 2000 platform with Simplecast feeding a live stream with multiple mount points. At scheduled points in the day, I have a scheduler that launches EZstream that overrides one of the mountpoints for a local 1 hour insert. Since we went back to standard time last weekend, the log entries in error.log have shown that the EZstream overrides have occurred one hour late, yet the system time was correct and I know that the overrides have occurred at the correct time. TZedit has been installed and the system is properly adjusting for the DST to standard time switch. I took a look at access.log and could see that the current entries in it were being entered as if the system clock were 1 hour advanced. I briefly shutdown Icecast, then restarted it and the new entries in the logs were correct. Both the system clock and my other application that launches EZstream were displaying the correct time. Only the Icecast log entries were off. So, where is Icecast getting its time for log entries? -- Dick Trump dtrump1 at triadav.com
Karl wrote:> Did you have windows changing the system/bios clock or did you have the > system/bios clock set to UTC with a timezone setting translating the > time to local time?The system/bios is set to the local time zone with Windows managing the DST. However, now that I think of it, I should mention that when installing TZedit last spring, I apparently set it to use the last Sunday in November, not the first. So, last Sunday morning when I happened to wake up after the change of time, I discovered that the time had not changed. I temporarily disabled the DST option to put the time right. Later that day (Sunday), I discovered the error I had made, corrected the entry with TZedit and turned the DST option back on. I looked at the system clock and the time displayed by my application that manages EZstream. Since both of the displayed the correct time, I assumed everything was OK. It could be that the temporary changes confused something, but it was surprising that the only thing that has seemed out of the ordinary were the log entries for Icecast. It's nothing that I feel I need to do anything about now, but it was certainly curious. If I remember, I'll check things next spring and report back if it doesn't seem to handle it correctly. -- Dick dtrump1@triadav.com
Dick Trump wrote:> I'm running Icecast 2.3.1 on a Windows 2000 platform with Simplecast feeding a live stream with multiple mount points. At scheduled points in the day, I have a scheduler that launches EZstream that overrides one of the mountpoints for a local 1 hour insert. > > Since we went back to standard time last weekend, the log entries in error.log have shown that the EZstream overrides have occurred one hour late, yet the system time was correct and I know that the overrides have occurred at the correct time. TZedit has been installed and the system is properly adjusting for the DST to standard time switch. > > I took a look at access.log and could see that the current entries in it were being entered as if the system clock were 1 hour advanced. I briefly shutdown Icecast, then restarted it and the new entries in the logs were correct. > > Both the system clock and my other application that launches EZstream were displaying the correct time. Only the Icecast log entries were off. So, where is Icecast getting its time for log entries? >Did you have windows changing the system/bios clock or did you have the system/bios clock set to UTC with a timezone setting translating the time to local time? karl.
Karl Heyes wrote:> Did you have windows changing the system/bios clock or did you have the > system/bios clock set to UTC with a timezone setting translating the time to > local time?Can you have the system clock set to UTC with Windows? My impression was that you couldn't. Geoff.