Re: [vdr] Turn off/relocate ts error logging

2009-08-30 Thread Klaus Schmidinger 
On 08/26/09 06:52, Timothy D. Lenz wrote:
From the auther of the atsc plugin:
 
 Yes, that's from the plugin. To fix it, find the following line in VDR's 
 channels.c
 
 Code:
 dsyslog(changing pids of channel %d from %d+%d=%d:%s:%s:%d to 
 %d+%d=%d:%s:%s:%d, Number(), vpid, ppid, vtype, OldApidsBuf,
 OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);
 
 and change it to
 
 Code:
 if (Number())
   dsyslog(changing pids of channel %d from %d+%d=%d:%s:%s:%d to 
 %d+%d=%d:%s:%s:%d, Number(), vpid, ppid, vtype, OldApidsBuf,
 OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);

Looks like there were several places where a check for Number() was missing.
The attached patch fixes this.

Klaus
--- channels.c	2009/08/16 15:08:49	2.7
+++ channels.c	2009/08/30 11:25:50
@@ -508,7 +508,8 @@
  q = NewSpidsBuf;
  q += IntArrayToString(q, Spids, 10, SLangs);
  *q = 0;
- dsyslog(changing pids of channel %d from %d+%d=%d:%s:%s:%d to %d+%d=%d:%s:%s:%d, Number(), vpid, ppid, vtype, OldApidsBuf, OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);
+ if (Number())
+dsyslog(changing pids of channel %d from %d+%d=%d:%s:%s:%d to %d+%d=%d:%s:%s:%d, Number(), vpid, ppid, vtype, OldApidsBuf, OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);
  vpid = Vpid;
  ppid = Ppid;
  vtype = Vtype;
@@ -558,7 +559,8 @@
  char NewCaIdsBuf[MAXCAIDS * 5 + 10];
  IntArrayToString(OldCaIdsBuf, caids, 16);
  IntArrayToString(NewCaIdsBuf, CaIds, 16);
- dsyslog(changing caids of channel %d from %s to %s, Number(), OldCaIdsBuf, NewCaIdsBuf);
+ if (Number())
+dsyslog(changing caids of channel %d from %s to %s, Number(), OldCaIdsBuf, NewCaIdsBuf);
  for (int i = 0; i = MAXCAIDS; i++) { // = to copy the terminating 0
  caids[i] = CaIds[i];
  if (!CaIds[i])
@@ -574,7 +576,7 @@
   if (Level  0) {
  modification |= CHANNELMOD_CA;
  Channels.SetModified();
- if (Level  1)
+ if (Number()  Level  1)
 dsyslog(changing ca descriptors of channel %d, Number());
  }
 }
@@ -622,7 +624,8 @@
  }
   else
  q += sprintf(q,  none);
-  dsyslog(buffer);
+  if (Number())
+ dsyslog(buffer);
 }
 
 void cChannel::SetRefChannel(cChannel *RefChannel)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Turn off/relocate ts error logging

2009-08-25 Thread Timothy D. Lenz 
From the auther of the atsc plugin:

Yes, that's from the plugin. To fix it, find the following line in VDR's 
channels.c

Code:
dsyslog(changing pids of channel %d from %d+%d=%d:%s:%s:%d to 
%d+%d=%d:%s:%s:%d, Number(), vpid, ppid, vtype, OldApidsBuf,
OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);

and change it to

Code:
if (Number())
  dsyslog(changing pids of channel %d from %d+%d=%d:%s:%s:%d to 
%d+%d=%d:%s:%s:%d, Number(), vpid, ppid, vtype, OldApidsBuf,
OldSpidsBuf, tpid, Vpid, Ppid, Vtype, NewApidsBuf, NewSpidsBuf, Tpid);

- Original Message - 
From: Klaus Schmidinger klaus.schmidin...@cadsoft.de
To: vdr@linuxtv.org
Sent: Sunday, August 23, 2009 1:26 PM
Subject: Re: [vdr] Turn off/relocate ts error logging


 On 23.08.2009 20:03, Timothy D. Lenz wrote:
  Form /var/log/user.log:
 
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8)

 This doesn't come from VDR (any more), because it no longer uses
 cTS2PES.

  But in looking at the log now with it having run a bit with good signal, I 
  find another log spam:
 
  Aug 23 10:44:18 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0
  Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
  Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0
  Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0
  Aug 23 10:45:21 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
  Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0
  Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0
  Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
  Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
  Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
  Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0
  Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
  Aug 23 10:47:06 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0
  Aug 23 10:47:27 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:47:48 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0
  Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
  Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0
  Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0
  Aug 23 10:48:51 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
  Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0
  Aug 23 10:49:12 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0
  Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
  Aug 23 10:49:33 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
  Aug 23 10:49:54 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:49:54 LLLx64-32 vdr: [2230

Re: [vdr] Turn off/relocate ts error logging

2009-08-24 Thread Timothy D. Lenz 
This is my complete channels.conf file:
:@1041
KVOA-DT,KVOA-DT:527028615:B6M10:T:0:49=2:0;52:0:0:3:0:211:0
:@1061
PBS HD,PBS HD:569028615:B6M10:T:0:49=2:0;52,56:0:0:1:0:213:0
:@1062
V-Me,V-Me:569028615:B6M10:T:0:65=2:0;68,72:0:0:2:0:213:0
:@1063
CREATE,CREATE:569028615:B6M10:T:0:81=2:0;84,88:0:0:3:0:213:0
:@1091
KGUN-DT,KGUN-DT:189028615:B6M10:T:0:49=2:0;52:0:0:3:0:215:0
:@1092
MEXI   ,MEXI   :189028615:B6M10:T:0:65=2:0;68:0:0:4:0:215:0
:@
KMSB,KMSB:539028615:B6M10:T:0:49=2:0;52:0:0:3:0:217:0
:@1131
KOLD-DT,KOLD-DT:213028615:B6M10:T:0:49=2:0;52:0:0:3:0:219:0
:@1132
Weather,Weather:213028615:B6M10:T:0:65=2:0;68:0:0:4:0:219:0
:@1133
Tube,Tube:213028615:B6M10:T:0:81=2:0;84:0:0:5:0:219:0
:@1181
KTTU-DT,KTTU-DT:503028615:B6M10:T:0:17=2:0;20:0:0:1:0:221:0
:@1271
PBS HD,PBS HD:557028615:B6M10:T:0:49=2:0;52,56:0:0:1:0:223:0
:@1272
KIDS,KIDS:557028615:B6M10:T:0:65=2:0;68,72:0:0:2:0:223:0
:@1273
WORLD,WORLD:557028615:B6M10:T:0:81=2:0;84:0:0:3:0:223:0
:@1401
KHRR-40, Telemundo Tucson, 
AZ,KHRR-DT:629028615:B6M10:T:0:49=2:0;52,54:0:0:3:0:225:0
:@1461
Univision,KUVE-DT:665028615:B6M10:T:0:49=2:0;52:0:0:1:0:179:0
:@1462
TeleFutura,KFTU-CA:665028615:B6M10:T:0:65=2:0;68:0:0:2:0:179:0
:@1581
KWBA-1,KWBA-1:653028615:B6M10:T:0:49=2:0;50:0:0:3:0:207:0
:@1582
KWBA-2,KWBA-2:653028615:B6M10:T:0:65=2:0;66:0:0:4:0:207:0

Adding a channel number to that last field (13) seems to cause problems with 
vdradmin getting guide data for the channels.

- Original Message - 
From: Klaus Schmidinger klaus.schmidin...@cadsoft.de
To: vdr@linuxtv.org
Sent: Sunday, August 23, 2009 1:26 PM
Subject: Re: [vdr] Turn off/relocate ts error logging


 On 23.08.2009 20:03, Timothy D. Lenz wrote:
  Form /var/log/user.log:
 
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8)

 This doesn't come from VDR (any more), because it no longer uses
 cTS2PES.

  But in looking at the log now with it having run a bit with good signal, I 
  find another log spam:
 
  Aug 23 10:44:18 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0
  Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
  Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0
  Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0
  Aug 23 10:45:21 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
  Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0
  Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0
  Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0
  Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
  Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0
  Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0
  Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
  Aug 23 10:47:06 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0
  Aug 23 10:47:27 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:47:48 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0
  Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0
  Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0
  Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 
  0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0
  Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids

Re: [vdr] Turn off/relocate ts error logging

2009-08-24 Thread Timothy D. Lenz 
for the TS error:

[14:01] rnissl simply comment out that line in vdr172_remux.c

../PLUGINS/src/xine-0.9.3/vdr172remux.c

- Original Message - 
From: Klaus Schmidinger klaus.schmidin...@cadsoft.de
To: vdr@linuxtv.org
Sent: Sunday, August 23, 2009 2:15 AM
Subject: Re: [vdr] Turn off/relocate ts error logging


 On 22.08.2009 19:12, Timothy D. Lenz wrote:
  My log files get so big it,s very hard to check them because of the ts 
  error messages that get flooded to it. I've had logs near
2gb
  in size. I have a problem with xine crashing when there is a weak signal 
  and the ts loging bloating the log files is creating a
lot
  of problems. Need a way to turn off ts error loging or relocate to another 
  file.

 Are these reports coming from the core VDR or from xine?

 Klaus

 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Turn off/relocate ts error logging

2009-08-23 Thread Klaus Schmidinger 
On 22.08.2009 19:12, Timothy D. Lenz wrote:
 My log files get so big it,s very hard to check them because of the ts error 
 messages that get flooded to it. I've had logs near 2gb
 in size. I have a problem with xine crashing when there is a weak signal and 
 the ts loging bloating the log files is creating a lot
 of problems. Need a way to turn off ts error loging or relocate to another 
 file.

Are these reports coming from the core VDR or from xine?

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Turn off/relocate ts error logging

2009-08-23 Thread Klaus Schmidinger 
/relocate ts error logging
 
 
 On 22.08.2009 19:12, Timothy D. Lenz wrote:
 My log files get so big it,s very hard to check them because of the ts 
 error messages that get flooded to it. I've had logs near
 2gb
 in size. I have a problem with xine crashing when there is a weak signal 
 and the ts loging bloating the log files is creating a
 lot
 of problems. Need a way to turn off ts error loging or relocate to another 
 file.
 Are these reports coming from the core VDR or from xine?

 Klaus
-- 
___

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

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Turn off/relocate ts error logging

2009-08-23 Thread Goga777 
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11)
  Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8)
 
 This doesn't come from VDR (any more), because it no longer uses
 cTS2PES.

do you mean - since vdr 179 this warning should disappear ?

with vdr 178 I have these warnings too

Aug 23 20:21:14 arvdr logger: waiting for in_discontinuity update #214
Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (2)
Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (1)
Aug 23 20:21:14 arvdr vdr: [3621] cAudioRepacker(0xC0): skipped 392 bytes to 
sync on next audio frame
Aug 23 20:21:14 arvdr vdr: [3621] PES packet shortened to 3286 bytes (expected: 
3470 bytes)
Aug 23 20:21:14 arvdr vdr: [3621] TS continuity error (4)
Aug 23 20:21:14 arvdr vdr: [3621] PES packet shortened to 3286 bytes (expected: 
3470 bytes)


Aug 23 20:21:17 arvdr logger: video_out: throwing away image with pts 55595230 
because it's too old (diff : 58615).
Aug 23 20:21:17 arvdr vdr: [3168] cTS2PES got 0 TS errors, 2 TS continuity 
errors
Aug 23 20:21:17 arvdr vdr: [3168] cTS2PES got 0 TS errors, 3 TS continuity 
errors
Aug 23 20:21:17 arvdr logger: input_vdr: flush buffers (vb: 0, ab: 0, vf: 0, 
af: 0) done.
Aug 23 20:21:17 arvdr vdr: [3622] TS buffer on device 1 thread ended (pid=3168, 
tid=3622)


Aug 23 20:47:05 arvdr vdr: [3189] Sent DISEQC command: t V W15 [E0 10 38 F3] 
W15 A W15 T
Aug 23 20:47:05 arvdr vdr: [4119] TS continuity error (7)
Aug 23 20:47:27 arvdr vdr: [3168] switching to channel 40


Aug 23 20:47:27 arvdr vdr: [3168] cTS2PES got 0 TS errors, 1 TS continuity 
errors









___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Turn off/relocate ts error logging

2009-08-22 Thread Timothy D. Lenz 
My log files get so big it,s very hard to check them because of the ts error 
messages that get flooded to it. I've had logs near 2gb
in size. I have a problem with xine crashing when there is a weak signal and 
the ts loging bloating the log files is creating a lot
of problems. Need a way to turn off ts error loging or relocate to another file.


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Turn off/relocate ts error logging

2009-08-22 Thread VDR User 
On Sat, Aug 22, 2009 at 10:12 AM, Timothy D. Lenztl...@vorgon.com wrote:
 My log files get so big it,s very hard to check them because of the ts error 
 messages that get flooded to it. I've had logs near 2gb
 in size. I have a problem with xine crashing when there is a weak signal and 
 the ts loging bloating the log files is creating a lot
 of problems. Need a way to turn off ts error loging or relocate to another 
 file.

You can use logrotate to limit the size of the log file.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr