>> I use the nice "set system time" feature of vdr. >> But sometimes vdr seems to read gabage time from DVB, I hereby vote to fix this. I lost a recording today because of time errors. See my (reduced) syslog: > Jun 25 19:00:06 vdr[947]: confirm: Taste dr?cken um Shutdown abzubrechen > Jun 25 19:01:09 vdr[1219]: System Time = Sat Jun 25 19:01:09 2005 (1119718869) > Jun 25 19:01:09 vdr[1219]: Local Time = Wed Jun 29 07:01:10 2005 (1120021270) > Jun 29 07:01:10 vdr[947]: confirmed > Jun 29 07:01:11 vdr[947]: executing '/usr/local/bin/vdrshutdown 1119734700 -286571 18 "Richling - Zwerch trifft Fell" 0' > Jun 29 07:01:13 nvram-wakeup[1434]: Do NOT write into nvram. Wake Up time must be > Jun 29 07:01:13 nvram-wakeup[1434]: at least 10 minutes in the future. > Jun 29 07:01:13 vdr[947]: deleting timer 19 (18 2325-0010 'Richling - Zwerch trifft Fell') > Jun 29 07:01:15 vdr[947]: SVDRP message: 'NVRAM-Wakeup failed...' > Jun 29 07:01:15 vdr[947]: info: NVRAM-Wakeup failed... > Jun 29 07:01:15 vdr[947]: closing SVDRP connection > Jun 29 07:01:16 vdr[1211]: System Time = Wed Jun 29 07:01:16 2005 (1120021276) > Jun 29 07:01:16 vdr[1211]: Local Time = Sat Jun 25 19:01:17 2005 (1119718877) > Jun 25 19:01:17 vdr[1219]: System Time = Wed Jun 29 07:01:16 2005 (1120021276) > Jun 25 19:01:17 vdr[1219]: Local Time = Sat Jun 25 19:01:17 2005 (1119718877) The machine kept running for another 9 hours with the 'NVRAM-Wakeup failed...' message on screen before I noticed this. Of course the timer 19 was not recorded, though the machine was running at that time. Cheers, Udo
