[mythtv-users] Recording starts soon, AUTO-Startup assumed (no it doesn't!)

[Graeme Wilford]

On 09/11/06, Thorsten Sandfuchs <fux at users.berlios.de> wrote:
> On Thu, Nov 09, 2006 at 04:34:09PM +0000, Graeme Wilford wrote:
> > Can someone explain the schedulers idle logic to me? I've read the
> > HOWTO and looked through scheduler.cpp but I'm a bit lost.
> > However, since then I restarted mythbackend several times and every
> > time I do, it logs
> >    Recording starts soon, AUTO-Startup assumed
> > despite the next recording being hours away (much longer than
>
> In my case the "AUTO-Startup" seems to be assumed on _every_ show mythtv
> considers in my "Upcoming Recordings" even in the duplicates and the reruns
> and not, as I'd expect it only in the "scheduled recordings".  I think this is
> a bug. Although mythtv shuts down the system, if the corresponding time of
> such a rerun did occure and the recording actually doesn't start.

I think you might be right. Although the scheduled recording was hours
away, there were non-recording duplicates and 'T' disabled recordings
within idleWaitForRecordingTime.

> > Does a minimum amount of time have to pass before mythbackend even
> > begins to consider itself idle? Also, why does it think that a
> > recording starts soon when in fact it's many hours away and
> > idleWaitForRecordingTime is set to 60 mins?
>
> perhaps you have a upcomming recording in every hour?

No, nothing like that and it did finally decide it was idle and
shutdown. By examining the logs, it looks to me like mythbackend only
tests for idle every 30mins at hr:00 and hr:30 (on the hour and at
half-past the hour) but that sounds too strange to be true...

Can anyone confirm, deny or explain this behaviour?

Thanks,
Wilf.
-- 
Me at google | MythTV blog: http://mezzanines.blogspot.com/