[mythtv-users] Slave Backend "currently not connected" after Master puts it to sleep
lfsmailing at gmail.com
Mon Jan 9 22:27:51 UTC 2012
I have the same problems (with myth 24.1)
> If I restart the master's mythtv-backend service, it wakes up the slave
> (which boots normally), and then shuts down the slave immediately.
> The problem is this: when the master shuts down the slave, it moves the
> status to "currently not connected" instead of asleep. So, recordings that
> should wake up the slave in the future are shown as conflicts.
> I can't seem to get the master to understand it should wake up the slave.
> Is there something I haven't configured correctly?
Has anyone got a setup like this working?
More information about the mythtv-users