<div class="gmail_quote">On Thu, Sep 30, 2010 at 4:09 PM, Ozzy Lash <span dir="ltr"><<a href="mailto:ozzy.lash@gmail.com">ozzy.lash@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Sep 30, 2010 at 1:07 PM, Ozzy Lash <<a href="mailto:ozzy.lash@gmail.com">ozzy.lash@gmail.com</a>> wrote:<br>
> I am running mythtv-0.23 from the debian multimedia repository. I<br>
> noticed in my monit.log that my cpu usage (the wait number) was<br>
> getting above the 20% threshold about every 3 hours, and I started<br>
> looking around for a cause. I finally looked that my mythfilldatabase<br>
> log, and notice it is running about ever three hours. (it looks to be<br>
> a few minutes over that). I think I have it set up to use the<br>
> suggested time from the grabber, but if I search the log for<br>
> NextSuggestedTime, it doesn't seem to be obeying that. Here is part<br>
> of the result of "grep NextSuggestedTime mythfilldatabase.log"<br></div></blockquote><div><br></div><div>Thank you for noticing this. I'm not sure how long this has been the case, but I just committed the fix for it into trunk, and it will be part of 0.24 when it's released. I'm sure TMS will appreciate the lower load that will present to their servers after we stop polling every 3h unintentionally.</div>
</div><br>