[mythtv-users] "I'm idle now... shutdown will occur..." messages during daily wakeup periods?

David Rees drees76 at gmail.com
Wed Apr 25 00:56:24 UTC 2007


On 4/24/07, Matt Doran <matt.doran at papercut.biz> wrote:
> Yes, this is the way the idle behaviour works.    It roughly works as
> follows:
>
>     * Backend determines that it's idle if a) it has no clients
>       connected, and b) there are no recordings happening.  At this
>       point it starts the idle countdown.
>     * Once the countdown reaches 0, it call "mythshudown --check" to see
>       if it's allowed to shutdown (i.e. it takes the wake up periods,
>       transcode/commflag jobs, etc into account)
>     * If the shutdown is denied, then the idle countdown starts again.
>       This happens over and over.
>
> It doesn't seem ideal to me, but it works ok.

Thanks for the information. It seems to we could save a lot of logging
by calling the `mythshutdown --check` before starting the countdown,
no? You might also want to doublecheck right before shutting down, but
I don't see that as being a huge issue...

> I've found one major problem with the approach.  If the countdown
> reaches 0, and one transcode/commflag job has completed, but the next
> has not yet started, the machine will be shutdown.  Even if there are
> many jobs waiting in the queue.  I've implemented a patch last night
> against trunk to fix this problem.  (See here:
> http://www.gossamer-threads.com/lists/mythtv/dev/265782)

Good to know!

-Dave


More information about the mythtv-users mailing list