[mythtv-users] X-Factor Scheduling Snafu

David Engel david at istwok.net
Wed Oct 19 20:25:53 UTC 2011

On Wed, Oct 19, 2011 at 02:48:39PM -0400, Jim Morton wrote:
> On 10/19/2011 2:35 PM, Roger Horner wrote:
> > On 11-10-19 11:59 AM, Brian J. Murrell wrote:
> >
> >> On 11-10-19 11:48 AM, Roger Horner wrote:
> >>> Since --dd-grab-all first deletes all your schedule data, if it starts just before you are about to record a program, wouldn't it cause you to miss the first 2 minutes of your program>(assuming it takes 2 minutes to run as Kris B. says) since without schedule data your BE no longer knows to record it?
> >> Hrm.  Is this really true?  This seems like a good case for building the
> >> new schedule before deleting the old one and keeping the "no schedule"
> >> time/lock to a very minimum while the already-built, new schedule is
> >> simply swapped in and the old one swapped out.
> > This was first brought up in
> > http://www.gossamer-threads.com/lists/mythtv/users/449445#449445 and I
> > haven't seen anything to say if it has been resolved.  If one of the devs could update the status on this, it would be greatly appreciated.
> >
> I can't imagine this would be the case. I think the scheduler would have 
> to run in that brief time
> the schedule itself was purged. Surely that has been considered and 
> coded for.
> I would throw out a guess that the scheduler likely will not run while 
> mythfilldatabase is running.
> If not I think we would have seen/heard of real life issues...
> Just my .02 worth. (from a non-dev)

There is currently no coordination between mythfilldatabase and the
scheduler other than mfdb forcing a full reschedule when it's done.
The way they work by default, however, makes the likelihood of a
problem very slim.  That's one of the reasons --dd-grab-all isn't the
default for mfdb.  Solutions to make --dd-grab-all be safer for
general use are being discussed.

David Engel
david at istwok.net

More information about the mythtv-users mailing list