Update about the "future issue":<br><div><br></div><div>Yesterday I've set a wake period for 12.30 (AM), and turned it off after midnight.</div><div><br></div><div>I've just checked if it was online and, yes, I could log in via ssh. It's about 11.15 (AM)</div>
<div><br></div><div>So I've looked in syslog to see at what time it woke up:</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><font face="'courier new', monospace">Feb 15 00:37:01 multisala kernel: Kernel logging (proc) stopped.</font></div>
</div><div><div><font face="'courier new', monospace">Feb 15 11:30:53 multisala kernel: imklog 4.2.0, log source = /proc/kmsg started.</font></div></div></blockquote><div><br></div><div>Ok, it woke up at 11.30, instead than 12.30</div>
<div><br></div><div>But.. WAIT: now it's 11.15! The "future" issue is still here, and NTPD is offline, I can't blame it.</div><div><br></div><div>So I decided to check why it's online. First, check mythshutdown to see why it's still online:</div>
<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><font face="'courier new', monospace">$ mythshutdown -c -s -v general</font></div></div><div><div><font face="'courier new', monospace"><br>
</font></div></div><div><div><font face="'courier new', monospace"><br></font></div></div><div><div><font face="'courier new', monospace">2012-02-15 11:15:12.824 Mythshutdown: --check</font></div></div><div>
<div><font face="'courier new', monospace">2012-02-15 11:15:12.824 Mythshutdown: --status</font></div></div><div><div><font face="'courier new', monospace">...</font></div></div><div><div><font face="'courier new', monospace">2012-02-15 11:15:12.937 Mythshutdown: --status returned: 0</font></div>
</div><div><div><font face="'courier new', monospace">2012-02-15 11:15:12.937 OK to shutdown</font></div></div><div><div><font face="'courier new', monospace">2012-02-15 11:15:12.937 Mythshutdown: --check returned: 0</font></div>
</div></blockquote><div><br></div><div>It shouldn't be online, let's see other logs... OH WAIT, now it's offline :/</div><div><br></div><div>Anyone have an idea of the reason why:</div><div>- I set a wakeup period at 12.30</div>
<div>- I found it woked up at 11.15</div><div>- It logs that he wake up ad 11.30</div><div><br></div><div>this thing is getting me mad worst than Daylight Saving Time issues in real life ;)</div><div><br></div><div><br></div>
<div><br><br><div class="gmail_quote">2012/2/14 ganassa <span dir="ltr"><<a href="mailto:ganassa@gmail.com">ganassa@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An update regarding this problem: yesterday I've encountered the same non-waking up problem again, in a random manner: I was expecting two wake-up moments, one in the morning and the other one in the afternoon. Well: for the first one scheduling the MythTv BE/FA woke up and recorded correctly, for the secondo one it didn't wake up at all.<div>
<br></div><div>So, while doing a further check, connecting and disconnecting via shh, I saw this:</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>~$ ssh multisala </div></div><div>
<div>datLinux multisala 2.6.35-32-generic #65-Ubuntu SMP Tue Jan 24 13:48:14 UTC 2012 i686 GNU/Linux</div></div><div><div>Ubuntu 10.10</div></div><div><div>...</div></div><div><div>No mail.</div></div><div><div><b>Last login: Tue Feb 14 01:58:57 2012 from lapsung</b></div>
</div><div><div>date</div></div><div><div>~$ date</div></div><div><div><b>Tue Feb 14 01:02:16 CET 2012</b></div></div></blockquote><div><div><br></div><div>In brief: the second time I logged into the BE/FE ssh reported that the last login was in the future!</div>
<div>So I realized that, probably, the problem isn't related to the MythTv/MythWelcome configuration but in something related to the time settings itself of the system, instead.</div><div>I've checked running processes and, yes, my backend was running 'ntpd'.</div>
<div>So I stopped and disabled at boot the NTP daemon . Let's see if I can blame it.</div><div><div class="h5"><div><br></div><div><br></div></div></div></div></blockquote></div></div>