<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 24, 2014 at 9:16 AM, Bill Meek <span dir="ltr"><<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 10/23/2014 10:54 PM, Hika van den Hoven wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I'm not familiar with the automated procedures. I know cut&past. But<br>
go with nano to the log (nano <path an name> and cut out irrelevancy!<br>
Or simply rm them and grap the fresh start!<br>
Also you can (I assume) cut out the wheat on the automatic paste!<br>
</blockquote>
<br></span>
As you've probably seen on this list, it's very common<br>
for users to paste what they believe to be the lines<br>
with errors.<br>
<br>
That may be OK, but it also means the lines at<br>
the beginning of the file that have the MythTV version<br>
(including the commit), are missing. As are the lines<br>
that show what loglevel and verbose options were used.<br>
<br>
So kudos to Daryl for providing the whole log. I was<br>
just trying to cut it down to the most recent run<br>
rather than 50K lines.<br>
<br>
Using the "rm" solution has caused problems for users<br>
on the list. Most recently, someone did it and then<br>
logging was shut off until the file was recreated<br>
(a permissions issue for that individual.)<br>
<br>
The other issue is with folded lines. My opinion is<br>
that if someone is asking for others to help them,<br>
then it's worth making the log easy to read. Here's<br>
an example of easy/hard:<br>
<br>
<a href="https://www.mythtv.org/wiki/Posting_Logs#Why_bother.3F" target="_blank">https://www.mythtv.org/wiki/<u></u>Posting_Logs#Why_bother.3F</a><br>
<br>
As has already been mentioned the best way to generate<br>
a log for a single run is to use the --logpath option.<br>
I start all my MythTV programs with it, but it requires<br>
more maintenance to keep the number of files from growing<br>
out of control. Distributions in my experience seem to<br>
choose --syslog and that makes perfect sense to me.<span class=""><font color="#888888"><br>
<br>
-- <br>
Bill</font></span><div class=""><div class="h5"><br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" target="_blank">http://wiki.mythtv.org/<u></u>Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" target="_blank">https://forum.mythtv.org</a></div></div></blockquote><div><br></div><div>Thanks for the patience and understanding, here are a couple appropriate sized logs:</div><div><br></div><div><div>daryl@daryl-A780L3C:~$ ./shortlog.sh mythbackend | pastebinit</div><div><a href="http://paste.ubuntu.com/8656900/">http://paste.ubuntu.com/8656900/</a></div><div>daryl@daryl-A780L3C:~$ ./shortlog.sh mythfrontend | pastebinit</div><div><a href="http://paste.ubuntu.com/8656903/">http://paste.ubuntu.com/8656903/</a></div><div>daryl@daryl-A780L3C:~$ </div></div><div><br></div><div>TIA Daryl</div><div><br></div><div> </div></div><br></div></div>