<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 4, 2013 at 12:18 AM, Daryl McDonald <span dir="ltr"><<a href="mailto:darylangela@gmail.com" target="_blank">darylangela@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"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div>On Tue, Sep 3, 2013 at 8:01 PM, 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"><div>On 09/03/2013 06:38 PM, Daryl McDonald wrote:<br>
...<br>
</div><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">
Ignore the previous paste bin it is some 61000 lines long and only goes<div><br>
until Aug 12th. Try this one instead: <a href="http://paste.ubuntu.com/6060751/" target="_blank">http://paste.ubuntu.com/<u></u>6060751/</a><br>
</div></blockquote>
<br>
Much better. If you look at line 11904, you'll see the backend starting a<br>
new run. The line just prior shows the backend stopping.<br>
<br>
In this case, you only need the last run.<br>
<br>
Now, look at line 12023. At 19:00 your time, the backend started recording<br>
something. So, there can't be an idle shutdown.<br>
<br>
Type and then look at the output of this command:<br>
<br>
mythshutdown -c<br>
<br>
It should tell you if it's OK to shutdown. If it says it's OK, then<br>
look at your backend logs or pastebin them if you like.<br>
<br>
It won't tell you if mythfrontend is running. So be sure to exit that<br>
before testing idle shutdown. [as Chris said earlier the frontend can<br>
be set to timeout, but I think the default is 90 minutes, so it's just<br>
easier to be sure it's not running]<br>
<br>
For the purposes of these tests, if you restart or power down your system,<br>
be sure to type: mythbackend --setverbose idle,system again to get the<br>
proper logging.<div><div><br>
<br>
-- <br>
Bill<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></div></div></blockquote></div></div><div>Here is a current backend.log: " <a href="http://paste.ubuntu.com/6061330/" target="_blank">http://paste.ubuntu.com/6061330/</a>"</div>
<span><font color="#888888">
<div><br></div><div>Daryl</div></font></span></div></div></div></blockquote><div><br></div><div>something else just occurred to me, in an attempt to satisfy the following suggestion from the Wiki: " You should check to make sure the user as whom mythbackend runs is able to run sudo without prompting for a password. Consult the documentation for sudo on how to set this up in the sudoers file, in particular the NOPASSWD tag. For example, you could add the following line to your /etc/sudoers by running "sudo visudo" and pasting the line at the end of the file." without actually checking the user permission (newbie inability showing) I simply stuck the line "%mythtv ALL = NOPASSWD: /sbin/shutdown, /usr/bin/setwakeup.sh" at the eend of my sudoers.d file. So that it now looks like this:</div>
<div><br></div><div><div>daryl@daryl-A780L3C:~$ sudo cat /etc/sudoers.d/README</div><div>[sudo] password for daryl: </div><div>#</div><div># As of Debian version 1.7.2p1-1, the default /etc/sudoers file created on</div><div>
# installation of the package now includes the directive:</div><div># </div><div># <span class="" style="white-space:pre"> </span>#includedir /etc/sudoers.d</div><div># </div><div># This will cause sudo to read and parse any files in the /etc/sudoers.d </div>
<div># directory that do not end in '~' or contain a '.' character.</div><div># </div><div># Note that there must be at least one file in the sudoers.d directory (this</div><div># one will do), and all files in this directory should be mode 0440.</div>
<div># </div><div># Note also, that because sudoers contents can vary widely, no attempt is </div><div># made to add this directive to existing sudoers files on upgrade. Feel free</div><div># to add the above directive to the end of your /etc/sudoers file to enable </div>
<div># this functionality for existing installations if you wish!</div><div>#%mythtv ALL = NOPASSWD: /sbin/shutdown, /usr/bin/setwakeup.sh</div><div>daryl@daryl-A780L3C:~$</div></div><div><br></div><div>Should this have been done?</div>
<div><br></div><div>Daryl</div>
</div><br></div></div>