[vdr] Re: Log of Timer Bug

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Marcus Kuba wrote:
> 
> Am 17.10.2001 18:32:25, schrieb Carsten Koch <Carsten.Koch@icem.de>:
> 
> >But even if I did, why would one of the 23:15h timers start at
> >23:37:56h and the other one at 23:40:06?
> 
> Good question... I never had timers that also stop immediately. They always started late
> and also stopped late. Klaus... can this be a timer-priority-issue? What's the default-
> behaviour when two timers with the same priority collide? Which one wins, the first or the
> last?

The first one wins.

> >Why would any timer start at a time that is not equal to the
> >time in the directory name?
> 
> If you were NOT using the watchdog, I'd say that vdr got stuck somewhere in its main-
> loop for a while and somehow got woken up (I have no idea how, but it happens after a
> while that it continues to work!), realized that the timer should be running but isn't and
> then started it. This was the case on my system... until I 'castrated' the watchdog and
> started using it :-)

I find it hard to believe that the main loop would get stuck for such a long time,
because if it gets stuck for more than 5 Minutes the "ERROR: time warp detected"
message should be triggered.

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________