[mythtv] in progress recordings and new scheduler

David Engel gigem at comcast.net
Wed Mar 17 00:23:06 EST 2004

On Tue, Mar 16, 2004 at 02:00:24PM -0800, Bruce Markey wrote:
> David Engel wrote:
> >The new ability to reactivate recordings should make this easier to
> >handle.
> I really like the reactivate button and have tested and used
> it. However it doesn't come into play here for a couple reasons.
> If the master is up'n'nunnin' but the slave crashes and is
> restarted, the scheduler is run when the slave reconnects but
> it makes no attempt to restart the recording. Instead, it simply

I said it makes it easier [to handle], not that it actually does it,

> >  If the slave should be doing something when it connects the
> >master can reactivate the recording and have the slave record the
> >remaining part of the program.  That still leaves some boundary cases
> >to consider, though.  How and how soon does the master know when a
> >slave goes away abnormally?  Should partial recordings be counted when
> >checking for duplicates?
> Opps, you snuck in a different state change. What to do when
> a slave disconnects is a different question than what to do
> when a slave connects.
> When a slave disconnects it might be a crash or it might be a
> network outage and the slave may be merrily recording away.
> It might be possible to have the master reassign the recording
> for the missing slave to another available card but this is
> full of pitfalls, messy and, believe it or not, I don't care 8-).
> So the master should probably ask each slave what it's up to
> each time a slave connects (when the master starts, there is a
> two second interval for the slaves to check-in before the first
> scheduler run). The scheduler could then account for recordings
> in progress while scheduling then restart anything that should
> be recording but isn't.

It sounds like you've got a good handle on what's needed.  Why don't
you do it? :-)

David Engel
gigem at comcast.net

More information about the mythtv-dev mailing list