I noticed that vdradmin showed yesterdays programinfo in "Playing today" page. Took a look in epg.data file and last update is more than 24 hours ago. I've made no changes to vdr and it has been working quite nicely some time now (seems like a bit more than 4 days this time). Timers are still working as they should. Actually everything else but epg.data seems to be working right.
First thought that maybe epg has not been updated but that would not seem to be propable for all the channels at the same time would it.
No log entrys at the time of the last update of epg.data.
Any ideas?
vdr 1.2.23 + subtitle 0.3.7
- Kartsa
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 13.5.2005
Kartsa wrote:
I noticed that vdradmin showed yesterdays programinfo in "Playing today" page. Took a look in epg.data file and last update is more than 24 hours ago. I've made no changes to vdr and it has been working quite nicely some time now (seems like a bit more than 4 days this time). Timers are still working as they should. Actually everything else but epg.data seems to be working right.
First thought that maybe epg has not been updated but that would not seem to be propable for all the channels at the same time would it.
No log entrys at the time of the last update of epg.data.
Any ideas?
vdr 1.2.23 + subtitle 0.3.7
I assume you mean VDR version 1.3.23 (there was no 1.2.23).
VDR saves the egp.data file every 10 minutes, unless there is
- an open menu - a running replay - an active recording - an active cutting process - an open SVDRP connection
Klaus
From: "Klaus Schmidinger" Klaus.Schmidinger@cadsoft.de
Kartsa wrote:
vdr 1.2.23 + subtitle 0.3.7
I assume you mean VDR version 1.3.23 (there was no 1.2.23).
Yep :) a small typo :D
VDR saves the egp.data file every 10 minutes, unless there is
- an open menu
- a running replay
- an active recording
- an active cutting process
- an open SVDRP connection
there were - no open menu - no running replay - no active recording - no active cutting process - no open SVDRP connection
I even restarted vdr and about 24 hours after that restart epg.data was suddenly updated. I was quite suprised. So suprised that I started to doubt my self about those activities if they were running or not.
- Kartsa
VDR saves the egp.data file every 10 minutes, unless there is
- an open menu
- a running replay
- an active recording
- an active cutting process
- an open SVDRP connection
Does this mean that an epg.data save process is skipped when one of this condition holds, and the next is tried exactly 10 minutes later? I have a program which opens an SVDRP connection (to query for active timers) exactly once per minute. Could that lead to the obvious unfortunate interaction with your 10 minute timer?
Olaf
Olaf Titz wrote:
VDR saves the egp.data file every 10 minutes, unless there is
- an open menu
- a running replay
- an active recording
- an active cutting process
- an open SVDRP connection
Does this mean that an epg.data save process is skipped when one of this condition holds, and the next is tried exactly 10 minutes later?
The check whether the epg.data file shall be saved (amoung other things) is done whenever none of the above conditions is true. See vdr.c:
if (!Interact && ((!cRecordControls::Active() && !cCutter::Active() && (!Interface->HasSVDRPConnection() || UserShutdown)) || ForceShutdown)) { time_t Now = time(NULL); if (Now - LastActivity > ACTIVITYTIMEOUT) { ... cSchedules::Cleanup(); ... } }
and
if (epgDataFileName && now - lastDump > 600) {
in epg.c.
So effectively the check is done every ten minutes, but may be postponed a short while if one of the conditions ist true. Of course, if such a condition is true for too long in one piece, egp.data may be saved much later - if at all.
Klaus
-
Kartsa -
Klaus Schmidinger -
Olaf Titz