[mythtv-users] Multiple backends
nick.rout at gmail.com
Thu Mar 24 18:56:39 UTC 2011
On Fri, Mar 25, 2011 at 7:14 AM, Tony Lill <ajlill at ajlc.waterloo.on.ca> wrote:
> Raymond Wagner <raymond at wagnerrp.com> writes:
>> On 3/20/2011 13:46, Tony Lill wrote:
>>> On 3/20/2011 11:50, Raymond Wagner wrote:
>>>> At current, the master backend requires a tuner card. With no tuner
>>>> card, the backend will shutdown, complaining about a failed sanity check
>>>> in the scheduler.
>>> You may want to rephrase that as "there must be a tuner card defined
>>> in the database". It doesn't even need to be on the master backend.
>> I thought it was more complex than that. I assumed the scheduler would
>> complain if there were no accessible tuners at the time of the check.
>> Slave backends will not have yet connected, and as such would not be
>> accessible. Either way, a tunerless backend has never been a supported
>> mode of operation. It was never designed for or tested, and as such may
>> result in inexplicable errors.
> Nope, on my last upgrade I ran a master backend and one frontend for
> weeks while I ported and tested my local fixes. I didn't connect
> anything with a tuner to the system until a couple days before the
> switchover. It seemed happy as a clam.
> I've run tunerless backends for years. You may not have officially
> tested it, but it seems to work. There may be issues trying to set one
> up from scratch, but once you have a working system, setting up
> tunerless slaves or promoting one of them to the master seems to work
Even if the master requires a tuner, could it not now (as of 0.24) be
one of the built in dummies?
More information about the mythtv-users