[vdr] Re: Vdradmin & autotimers running wild

[Tom Pfeifer <pfeifer@fokus.fraunhofer.de>]

On Mon, Oct 27, 2003 at 07:28:38PM +0200, Jan Ekholm wrote:
> 
> http://www.infa.abo.fi/~chakie/media/dvb/vdradmin3.jpg
> 
> Two programs, starting at 10:10 and 10:35. So far so good. But running
> AutoTimers on those two shows (have done that for half a year now), I get
> this result:

These 2-hour shifts seem to be typical for the summer/wintertime switch,
which is kind of hardcoded ($isdst) in the vdradmin:

sub my_mktime {
        my $sec  = 0;
        my $min = shift;
        my $hour = shift;
        my $mday = shift;
        my $mon  = shift;
        my $year = shift() - 1900;

        my $isdst = 1;
        my $time = mktime($sec, $min, $hour, $mday, $mon, $year, 0, 0, $isdst);

As discussed in the thread "[vdr] Re: vdradmin-problem summertime"
this can be fixed by setting 
my $isdst = 0;

However, we should ask Thomas Koch why this is hardcoded into the code.

> http://www.infa.abo.fi/~chakie/media/dvb/vdradmin2.jpg
> 
> The times are well out in the woods. I've restarted VDRadmin and VDR, so
> it should not be a "winter time" error. Each time the AutoTimers are run
> one new timer (where the time is usually a few hours off) is created. I
> now spend some time each day to try and nuke all the extra timers, but
> as I update only once every 3 hours, there is only 7-8 wrong timers per
> day, which isn't too much.

Maybe this has the same reason, that vdradmin/autotimer gets confused 
by the wrong timers it created, and generates new ones?

-- 
Viele Grüße
Tom Pfeifer



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.