Re: [vdr] Timeouts and lost locks

2009-05-24 Thread Jan Ekholm
On Saturday 23 May 2009 12:47:49 Klaus Schmidinger wrote: > EPG data is always collected for the transponders you actually tune to. > The EPG scan just automatically switches through all transponders, which > is apparently not what you want. > > You could also remove all unwanted channels from you

Re: [vdr] Timeouts and lost locks

2009-05-23 Thread Klaus Schmidinger
On 05/23/09 11:42, Jan Ekholm wrote: > On Friday 22 May 2009 14:22:16 Klaus Schmidinger wrote: >> On 22.05.2009 09:07, Jan Ekholm wrote: >>> Good morning, >>> >>> I see logging like this all the time in my syslog file: >>> >>> May 22 06:36:45 hex vdr: [31292] frontend 0 timed out while tuning to >>

Re: [vdr] Timeouts and lost locks

2009-05-23 Thread Jan Ekholm
On Friday 22 May 2009 14:22:16 Klaus Schmidinger wrote: > On 22.05.2009 09:07, Jan Ekholm wrote: > > Good morning, > > > > I see logging like this all the time in my syslog file: > > > > May 22 06:36:45 hex vdr: [31292] frontend 0 timed out while tuning to > > channel 31, tp 298 > > May 22 06:37:06

Re: [vdr] Timeouts and lost locks

2009-05-22 Thread Tony Houghton
On Fri, 22 May 2009 16:38:36 +0300 Lauri Tischler wrote: > Tony Houghton wrote: > > > It would also be nice if > > VDR had a logfile to itself instead of syslog. > > Fix your syslogd and RTFM :) > > -l level, --log=level > > Set logging to level. 0 = no logging, 1 = errors only, 2 = errors an

Re: [vdr] Timeouts and lost locks

2009-05-22 Thread Lauri Tischler
Tony Houghton wrote: > It would also be nice if > VDR had a logfile to itself instead of syslog. Fix your syslogd and RTFM :) -l level, --log=level Set logging to level. 0 = no logging, 1 = errors only, 2 = errors and info, 3 = errors, info and debug. The default logging level is 3. If logging

Re: [vdr] Timeouts and lost locks

2009-05-22 Thread Tony Houghton
On Fri, 22 May 2009 13:22:16 +0200 Klaus Schmidinger wrote: > Well, I'm still working on the code that reads the user's mind and > determines what they might find "interesting" ;-) Have you thought about a keyed logging system? It would also be nice if VDR had a logfile to itself instead of sysl

Re: [vdr] Timeouts and lost locks

2009-05-22 Thread Klaus Schmidinger
On 22.05.2009 09:07, Jan Ekholm wrote: > Good morning, > > I see logging like this all the time in my syslog file: > > May 22 06:36:45 hex vdr: [31292] frontend 0 timed out while tuning to channel > 31, tp 298 > May 22 06:37:06 hex vdr: [31292] frontend 0 timed out while tuning to channel > 33,

[vdr] Timeouts and lost locks

2009-05-22 Thread Jan Ekholm
Good morning, I see logging like this all the time in my syslog file: May 22 06:36:45 hex vdr: [31292] frontend 0 timed out while tuning to channel 31, tp 298 May 22 06:37:06 hex vdr: [31292] frontend 0 timed out while tuning to channel 33, tp 322 And: May 22 09:59:58 hex vdr: [31292] fronte