Hi nephster,
thanks for your post, this is very important for me in order to improve both the program and also the documentation. Some remarks to your input:
The most trouble I had was actually with getting the windows client working. I suspect the default subnet should be 255.255.255.255 rather than its current value for most people? That was what I had to spend 30mins playing around with!
Actually what you set in the windows client is the broadcast address. It shouldn't be called "Subnet" in the config dialog, so thanks for pointing this out. I will change the name of the field in the next version of the client.
So, for instance, if your private network is in the 192.168.0.0 / 24 range, the setting has to be 192.168.0.255. I'll try and see if there is a way to automatically detect this in a way that it gets easier for the users to configure.
In the wiki, you talk about checking if "hosts" are connected. Shouldn't that be "clients"? The Amahi box is the host, surely.
Again thanks for pointing this out. A "host" is simply a computer with a network termination, so strictly speaking both the Amahi box and whatever other computer are hosts. But again I agree, the term "client" is maybe more understandable in the context of AES. I will change this in one of the upcoming versions.
EDIT: Been thinking about this a little more, my conclusion is that "host" is really the correct term, so instead of changing the AES I will update the wiki to better explain what is meant.
Anyway, this is wonderful. What I'd love is some windows client to suspend the Fedora box with a click if I know I don't need it. At the mo it's fire up Putty, login as root, and pm-suspend (or walk next door!).
What should happen is that the Amahi box goes to sleep some time after all clients are shutdown, no more file access, etc. Clarification question: So what you request is a button to shut down the Amahi box immediately?
Problem with logging in and fireing pm-suspend is that AES has no contol over the shutdown. There are some drawbacks with this, for instance the box will not wake up for scheduled events. So it's acutally not recommended to do this kind of "manual" shutdown.
Or, does your machine stay awake until forever? This should not be the case, it should go down latest about 10 minutes after there has been no access.
Keeps those comments coming!
/jayrock