On 9/17/07, <b class="gmail_sendername">Michael T. Dean</b> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 09/17/2007 04:49 PM, Patrick Wagstrom wrote:<br>> Cottrell, Eric wrote:<br>><br>>>> OK, I may be blind, but...<br>>>> This morning when I checked the schedules, I found that<br>>>> mythtv didnt know anything about what was on the air.
<br><br><snip><br><br>> Sounds like mythfilldatabase not automatically running may be a<br>> moderately common issue.<br><br>Perhaps you two, too, are suffering from the issue that I described in<br>Eric's thread (if so--if the below solutioin fixes the issue for any/all
<br>of you), please let me know as I can probably make a case for getting a<br>"fix" into 0.20-fixes). I'll re-post my answer here since it hasn't yet<br>made it into the archives:<br><br>It sounds like you may be using the "Run mythfilldatabase at time
<br>suggested by grabber" but the time that was last suggested (i.e. by a<br>"manual" execution of mythfilldatabase) is not in the window during<br>which mythfilldatabase is allowed to run. To fix it, change the
<br>"mythfilldatabase Execution Start/End" times to 0 and 24, respectively.<br><br>In 0.20.2 (and 0.20-fixes), the window is "moved" to a period of a<br>couple of hours around the suggested time by the backend when the
<br>backend runs mythfilldatabase. So, if mythfilldatabase is run manually,<br>no one is updating the window and it may or may not line up with the<br>last-updated window. In SVN trunk (and, in 0.21, when it's released),
<br>the window isn't changed, rather it's ignored. See<br><a href="http://www.gossamer-threads.com/lists/mythtv/commits/263447#263447">http://www.gossamer-threads.com/lists/mythtv/commits/263447#263447</a> .<br></blockquote>
</div><br><br>Mike,<br><br>While we're talking about the automatic mythfilldatabase (MFDB) controls, <br>perhaps you (or someone else, for that matter) can clear up another aspect <br>for me. If I have the automatic scheduling of MFDB enabled and then use
<br>the mythwelcome/mythshutdown controls to send my system into suspend <br>or hibernate, AKA suspend to ram or suspend to disk, will it wake up when <br>the MFDB is scheduled to run (presuming that that is before the next
<br>scheduled recording event)? In other words, is the wakeup time fed to <br>mythshutdown taking into account *both* the time of the next recording<br>*and* the time of the scheduled MFDB job? Section 11.5 of the <br>documentation in
<a href="http://www.mythtv.org/modules.php?name=MythInstall">"Installing and using MythTV"</a> doesn't make any mention <br>of the MFDB time, so it has been my assumption that it isn't accounted for. <br>
Hence, I have not tried the automatic MFDB feature and instead have bashed <br>together a script to extract the suggested time from the MFDB log and choose<br>the earlier of that time and the time supplied by mythshutdown (my script is
<br>masquerading as the nvram-wakeup command used to set the alarm time).<br>If I've reinvented the wheel, I'd be happy to trade in my wagon wheel for <br>a modern tubeless tire. ;-)<br><br>OTOH, if it's not taken into account, do I need to go to the -dev list or submit
<br>a bug report to have this considered for an enhancement to the code?<br><br>Craig.<br>