<br><br><div><span class="gmail_quote">On 22/11/2007, <b class="gmail_sendername">Paul Harrison</b> <<a href="mailto:mythtv@dsl.pipex.com">mythtv@dsl.pipex.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Paul Mason wrote:<br>> At the beginning of the month I set up my mythtv box to<br>> shutdown/wakeup automatically using ACPI, mythshutdown and<br>> mythwelcome. Prior to that it was running 24/7.<br>><br>> I have a cron job which does a db backup, optimize, xfs defrag etc -
<br>> which is set to run daily at 3am. In order to allow for this I've set<br>> one of the wake-up periods to 2:45 - 3:45. I've also put a<br>> "mythshutdown --lock" at the top of my script and a "mythshutdown
<br>> --unlock" at the bottom.<br>><br>> I use the other wake-up period to have the box awake during my main<br>> viewing period - 19:00 - 23:59 (the box is both BE and FE).<br>><br>> So far so good. I set it up following the wiki with very little
<br>> trouble and it's been working perfectly. Or so I thought. It always<br>> wakes up for recordings, it always wakes up for 19:00 but it hasn't<br>> been waking up for 2:45. I hadn't realised this until last night
<br>> because often it had been still awake running a job after a recording,<br>> so the backups were getting done (mostly).<br>><br>> Anyway I've been looking into this, searching the archives of this<br>
> list, the wiki and elsewhere and I can't find any report of a similar<br>> problem, or any note of why one of the wakeup periods would work but<br>> not the other. The script I use to set the wakeup time in the BIOS
<br>> writes to a log, so I can see that it never gets called for the 2:45<br>> wakeup.<br>><br>> The only thought I had was whether the wakeup periods need to be in<br>> order i.e. at the moment period1 is 19:00 - 23:59 and period2 is 02:45
<br>> - 03:45 - perhaps I need to switch them? I'll try that tonight in any<br>> case.<br>><br>> I'm running SVN trunk from about a couple months ago. (I also searched<br>> Trac but didn't find anything on this)
<br>><br>> --<br>> Paul Mason<br><br>I wasn't aware of having to have the wakeup periods in the correct order<br>but it looks like you could be right. Basically what happens is if the<br>start times for both daily wakeup periods has passed for today then the
<br>next wake time will be set to the first daily wakeup time tomorrow even<br>if the second daily wakeup time is before the first. There should really<br>be a check to make sure that the earliest daily wakeup time is used.
<br>Swapping the period around should fix things for now.</blockquote><div><br><br>Thanks. Yes that confirms what I just discovered. It's one of those things that doesn't necessarily need fixing but it perhaps needs documenting. So I updated the wiki to reflect this.
<br></div></div><br clear="all">Thanks again<br>-- <br>Paul Mason