[mythtv-users] Encoder (slave) "currently not connected" or "currently asleep"?

[Ma Begaj]

2009/11/4 Mike Perkins <mikep at randomtraveller.org.uk>:
> Chris Pinkham wrote:
>>
>> * On Tue Nov 03, 2009 at 08:02:40AM +0100, Ma Begaj wrote:
>>>>
>>>> In essence, if you use the on-demand wakup/shutdown functionality for
>>>> slave
>>>> backends, don't shut them down yourself, you need to let the master
>>>> backend
>>>> tell the slave to shutdown.
>>>>
>>> Thanks. Helpful as always.
>>
>> One other thing I didn't mention.  It is on my TODO list to add a way to
>> allow
>> a slave backend to tell the master that it is going to sleep, so you could
>> shutdown the slave and have the master wake it back up again.  This is
>> primarily for combination FE/SBE machines, so the user can shutdown the
>> machine when done use the FE and have the master wake the slave back up if
>> necessary to record something new.
>>
> I was wondering about that. I have a workstation which I would contemplate
> putting a back end in if I knew the MBE would understand the various states
> it could be in.
>
> 1. Me working and SBE available, manually started and stopped.
> 2. SBE invoked by master, recording and shut down afterwards.
> 3. Powered down by me, but available if MBE requires it (woken up by WOL
> code).
>
> Obviously, there could be times when I went to shut it down while it was
> recording, where it would need to remain awake until the recording+optional
> processing had finished, then shut itself down. Presumably this could be
> achieved by the use of a cunning script. Thoughts?
>

I solved this temporary by setting wakeup time on slave backend
before shutdown.

Slave will wake up independently without Master and it will connect to
Master after starting itself. No recordings will be missed.