myllymaa at niksula.hut.fi
Thu Feb 16 09:51:02 CET 2006
On Wed, 15 Feb 2006, Jouni Karvo wrote:
> Marko Myllymaa writes:
> > I tried "NO_EVENTID = 1" with earlier vdradmind version, but I had to turn
> > it to 0 again. Now I didn't got double timers, but about 15 times every
> > timer... Hopefully it works better with my current version.
> Yes - the latest AM version fixed this for me.
I tried "NO_EVENTID_ON = 4", but I still got second galactica timer. This
time also to saturday, though it should have been only on fridays.
I'm using vdradmin-am-3.4.3rc2 and vdr-1.3.23.
Is there anything I can do to track this down?
Here are corresponding timer lines for those galacticas:
First one is the correct one.
And I still have autotimer set to fridays only.
Below is some lines from vdradmind.log matching "Galactica" and from such
time that false timer is programmed:
02/15/06 18:41:28: ProgTimer: Programming Timer "Taisteluplaneetta
Galactica" (Channel 4, Event-ID 0, 20060218-2341 - 20060219-0145, Active 32769)
02/15/06 18:41:32: AutoTimer: Programming Timer "Taisteluplaneetta
Galactica" (Event-ID 361, 20060217-2335 - 20060218-0035)
02/15/06 18:41:32: AT_ProgTimer: Programming Timer "Taisteluplaneetta
Galactica" (Event-ID 361, 20060217-2331 - 20060218-0045)
02/15/06 18:41:32: ProgTimer: Programming Timer "Taisteluplaneetta
Galactica" (Channel 4, Event-ID 0, 20060217-2331 - 20060218-0045, Active 32769)
I have some questions about those lines. What's the difference between
ProgTimer, Autotimer and AT_ProgTimer? And when does Event-ID get value
More information about the vdr