[mythtv-users] Nothing to record, but no Idle/Shutdown

[David Watkins]

On 01/06/06, Mercury Morris <mercury.morris at gmail.com> wrote:
> Running MythTV 0.19.20060331-1, I have it configured to shutdown
> the system when the frontend is stopped.  That is, unless there
> is something to record coming up within the specified interval.
> By "specified interval", I mean "Max wait time for recording(min)".
>
> But here is the behavior observed over the last few nights, nights
> when there is nothing to record because all the Upcoming Recordings
> are marked 'r' or 'P' (repeat or Previously recorded).
>
> If the frontend is stopped when there is more time than the
> specified interval, the backend reports:
>
>  2006-05-29 10:00:07.705 I'm idle now... shutdown will occur in 180 seconds.
>
> And, as expected, the machine shuts down in 180 seconds.
>
> But, if the frontend is stopped when there is less time than
> the specified interval, the backend takes no notice and just
> continues to wait for the recording start time to arrive.
>
> BUT, there are no programs to record!  Shouldn't the backend
> realize that there is nothing to record and shutdown the system?
>
> This really stumped me, so I rebooted the machine, watching the
> backend log.  I was shocked to see the backend report that
>
>  2006-05-29 10:10:19.139 Recording starts soon, AUTO-Startup assumed
>
> And again, the backend just sat there, waiting for the recording
> start time to arrive, still with nothing to be recorded.
>
> If this behavior is the actual design, then I accept it.  But I
> at least have to ask the question, since the machine could be shut
> down sooner, rather than waiting until "non-recording" time arrives.


I doubt that this is by design and suspect that there's scope for
someone to roll their sleeves up and do a bit of tidying up.  If you
feel up to it then I've another couple of symptoms that you could look
at:

Manually starting the backend during a scheduled recording that will
not be recorded ( due to the episode record limit being reached in my
case but probably for 'repeat' or 'Previous' also) causes the machine
to assume an auto start up, hence not start a frontend,  and shut
straight down again.

The programmed wake-up time does not take account of the "Start Late"
offset.  Luckily, because of the issue that you have noted, when the
backend wakes up early it doesn't shut itself down before the
recording is due to actually start.

Good Luck