<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br><div><br></div></div><div><br>On Apr 2, 2014, at 11:23, david brooke <<a href="mailto:david2012brooke@gmail.com">david2012brooke@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 1, 2014 at 10:49 PM, Bill Meek <span dir="ltr"><<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You've not asked for any logging other that the default that prints to<br>
the console. Use mythfrontend --help to see your options, or see this<br>
Wiki for more detail: <a href="http://www.mythtv.org/wiki/Logging" target="_blank">http://www.mythtv.org/wiki/<u></u>Logging</a><br>
<br>
Here are 2 examples:<br>
<br>
mythfrontend --quiet --logpath /var/log/mythtv<br>
mythfrontend --quiet --syslog local7<br>
<br>
I prefer the 1st, but that will generate an individual log every time you<br>
start the frontend. --quiet shuts off console logging which isn't necessary<br>
if you're logging elsewhere. You don't have to use it.<br>
<br>
An Arch user will have to chime in if mythfrontend is a wrapper script that<br>
executes something else. In which case, that script could set the logging<br>
for you.</blockquote><div><br></div><div>If someone from Arch could comment on the proper way to initiate the log in both mythfrontend and mythbackend, it would be appreciated.<br></div><div>Thanks</div></div></div></div></blockquote><br><div>Figure out what runs those applications, be it a script, shortcut, whatever. Edit it to add the appropriate arguments.</div></body></html>