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.Schmidinger@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] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:50:16 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:50:16 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:50:16 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:50:36 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
Don't know if that is VDR or something the atsc plugin is causing.
I don't have any such messages with "channel 0" in any of my logs here.
Klaus
----- Original Message ----- From: "Klaus Schmidinger" Klaus.Schmidinger@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
-- _______________________________________________________________
Klaus Schmidinger Phone: +49-8635-6989-10 CadSoft Computer GmbH Fax: +49-8635-6989-40 Hofmark 2 Email: kls@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