Hi Uwe,
I can remember there was an issue some time ago with restarting VDR when a tvtv timer update starts... But at the moment, tvtv (0.2.13a) together with VDR 1.4.1 works well on my machine.
To fix the problem, try to delete one timer after the other on tvtv until the restarting problem disapear. Maybe it is just one corrupted timer...
Schimmi
IT schrieb am Sonntag, 18. Juni 2006 um 11:55:
> Hi,
> I'm using VDR version 1.3.49 with tvtv (0.2.13a)
> As soon as I start the tvtv update I get this message:
> Jun 18 11:52:03 bremen vdr: [6386] confirm: TVTV update wird ausgeführt
> Jun 18 11:52:03 bremen vdr: [6386] warning: TVTV update wird ausgeführt
> Jun 18 11:52:03 bremen vdr: [8587] TVTV: Timer Thread started (pid=6386)
> Jun 18 11:52:03 bremen vdr: [8587] TVTV: Timer Update started
> Jun 18 11:52:04 bremen vdr: [8587] TVTV: Received 8623 Bytes
> Jun 18 11:52:04 bremen vdr: [8587] TVTV: Processing CSV data
> Jun 18 11:52:04 bremen vdr: [8587] TVTV: Found 17 fields in CSV data
> Jun 18 11:52:04 bremen vdr: [8587] TVTV: Start reading timer jobs
> Jun 18 11:52:04 bremen vdr: [8587] TVTV: Received 'Premiere
> Krimi,936,26209874,2006-06-23 20:15:00 +0200,2006-06-23 22:00:00
> +0200,...'
> Jun 18 11:52:04 bremen runvdrdevel: restarting VDR
> I remember there was an issue with the field length some time ago in
> tvtv - but thought it is fixed
> Can anybody help?
> Thanks
> uwe
> _______________________________________________
> vdr mailing list