WOL and keep backend alive

[minidroidboy]

I have logged a potential enhancement as Issue 82, for folk who have
their backend sleep when not in use, as I do.

1. Backend mac address needs storing.
2. mdd command in mdd.conf
3. script to lock/unlock mythshutdown.
4. Wake backend and keep it alive until mythdroid is closed.
5. As frontend is woken, send magic packet to backend.
(Frontend currently wakes backend, but will be quicker if woken
simultaneously. Frontend keeps backend alive until it closes)

Here's what I've kludged so far :-

1. I've put the backend in as a frontend (mac and ip) - temporary
2. command =KeepAlive=>/usr/bin/keepalive.sh in mdd.conf
3. shell script to lock mythshutdown, sleep, unlock mythshutdown
4. ?????

Now, the rub is, mdd commands can't be run on a backend only install
of mdd - I have tested the rest on a frontend, and seems to be working
as I'd expect.
I can wake the backend, using WOL (kludged as frontend)
I can run the script on a frontend using mdd command.

So, i need to
a. have the backend listen for and execute mdd commands.
b. have mythdroid wake the backend, then periodically, run the mdd
command to keep the backend up.
c. have mythdroid send magic packet to b/e when it wakes a f/e

I have, so far, done no investigation into the differences of a f/e b/
e install of mdd.
I will investigate these differences, and have a gander at the
mythdroid code to see what I can come up with. (It's been a long time
since I've done any coding and have no experience with java, but hey-
ho!)

If anyone has any pointers/suggestions, they will be gratefully
received, and probably save a lot of time!

[minidroidboy]

OK - have done a bit of digging:
It appears that mythdroid connects to the b/e as a client, therefore
will keep it alive whilst connected.
This removes the need for the b/e to execute mdd commands (at the
moment - i will look into this further, as I can see a couple of
opportunities with it)

However, I can not ascertain when this connection as client is
terminated. If I close mythdroid on the phone, the client connnection
appears to persist, thus not allowing the b/e to shutdown - further
investigation needed.

>
> 1. Backend mac address needs storing.(as b/e not frontend)
> 4. Wake backend (as b/e not f/e)

[foo bar]

Hey,

On 2 December 2011 11:21, minidroidboy <minidr...@gmail.com> wrote:

However, I can not ascertain when this connection as client is
terminated. If I close mythdroid on the phone, the client connnection
appears to persist, thus not allowing the b/e to shutdown - further
investigation needed.

A recent change means that we hang on the be connection indefinitely in an attempt to solve some potential issues.

Better solution required.. I'll have a look. 

 

> 1. Backend mac address needs storing.(as b/e not frontend)
> 4. Wake backend (as b/e not f/e)

> 5. As frontend is woken, send magic packet to backend.

Ok, yeah, we probably need some mechanism for waking up backends.. I'll look at this too.

Regards,

foobum