[vdr] Re: Timer Bug in vdr?

[Usenet-372111@zocki.toppoint.de (Rainer Zocholl)]

Thorsten.Thomas.Heck@t-online.de(Thorsten Heck)  22.09.01 16:59

Once upon a time Thorsten Heck shaped the electrons to say...

>Hi!

>I just thought someone cracked my machine and was switching channels
>for me, but it was vdr 0.95 :-)

Had a similar effect:
On tuesday VDR tries to record events from monday, and
find one second later, that those records need not yet to be done.

I have the feeling that the staring thread sees another systemtime
that the rest of the world.



>Timer 3 in my timers.conf looks like this:
>1:3:MDMDF--:1600:1701:50:50:Star Trek - Das nächste Jahrhundert:

>And this is what vdr did:

>Sep 22 16:37:29 linux vdr[21296]: timer 3 start
>Sep 22 16:37:29 linux vdr[21296]: switching to channel 3
>Sep 22 16:37:29 linux kernel: mon_complete(0): freq=1880000000, sr=27500000, realfreq=1880000000, step=1 , fdiff=0, fec=0
>Sep 22 16:37:29 linux vdr[21296]: Title: 'Family Law' Subtitle: 'Fahrerflucht'
>Sep 22 16:37:29 linux vdr[21296]: record /video0/Star_Trek_-_Das_nächste_Jahrhundert/Fahrerflucht/2001-09-22.16.00.50.50.rec
>Sep 22 16:37:29 linux vdr[21296]: creating directory /video0/Star_Trek_-_Das_nächste_Jahrhundert/Fahrerflucht
>Sep 22 16:37:29 linux vdr[21296]: creating directory /video0/Star_Trek_-_Das_nächste_Jahrhundert/Fahrerflucht/2001-09-22.16.00.50.50.rec
>Sep 22 16:37:30 linux vdr[21296]: recording to '/video0/Star_Trek_-_Das_nächste_Jahrhundert/Fahrerflucht/2001-09-22.16.00.50.50.rec/001.vdr'
>Sep 22 16:37:30 linux vdr[28095]: output thread started (pid=28095)
>Sep 22 16:37:30 linux vdr[28096]: input thread started (pid=28096)
>Sep 22 16:37:35 linux vdr[28095]: output thread ended (pid=28095)
>Sep 22 16:37:35 linux vdr[28096]: input thread ended (pid=28096)
>Sep 22 16:37:36 linux vdr[21296]: buffer stats: 37600 (3%) used
>Sep 22 16:37:36 linux vdr[21296]: timer 3 stop
>
>Vdr didn't crash and restart or something, it was happily running for several 
>hours now...