[mythtv-users] User job runs on wrong backend

mikp mikpolniak at roadrunner.com
Fri Apr 3 21:13:52 UTC 2009


On Fri, 3 Apr 2009 21:59:26 +0100
Andre Newman <mythtv-list at dinkum.org.uk> wrote:

> 
> On 3 Apr 2009, at 21:28, mikp wrote:
> 
> > On Fri, 3 Apr 2009 18:33:38 +0100
> > Andre Newman <mythtv-list at dinkum.org.uk> wrote:
> >
> >>
> >> On 3 Apr 2009, at 18:26, Michael T. Dean wrote:
> >>>>
> >>>> Any clues as to where to look next?
> >>>
> >>> In mythtv-setup:
> >>>
> >>> Run Jobs only on original recording backend
> >>> If set, jobs in the queue will be required to run on the backend
> >>> that made the original recording.
> >>
> >> Found that and it's on already, that's why I'm running out of ideas!
> >> Checked on both backends, although I think it's a global setting.
> >>
> >> Anything else that might affect this?
> >>
> > I filed a Ticket for a similar problem with my slave backend running  
> > its commflagging jobs on the master backend.
> > Short answer:
> > "Run Jobs only on original recording backend" applies only to the  
> > master BE not a slave
> 
> Ah thank you, glad to know I'm not going mad.
> 
> I'm getting master user jobs (trying) running on the slave too.
> I'll have to find another way around as I doubt I'm up to fixing it.
> 
To keep the slave BE jobs from running frequently on the master BE, i set the
JobQueueCheckFrequency to a few seconds on the slave and a large number on
the master.


More information about the mythtv-users mailing list