[1.32 - 1.4] "Wake on Lan" command/api/program

I think that would be great to have a command/program/api to remotely turn on (or off?) an specific computer (Wake on Lan).
Otherwise I have to turn on/off manually my 15-20 PC (GPS net, monitoring, etc) when I need them.

Every pc should have a white-list (what pc are allowed to turn on). The "wakeOnLan" command should have a parameter that allow to execute a startup programs (avoiding startup file modifications thing…) like monitor api.

Computer's save their on/off state…. if you exit the game with the computer on, it should be on (rebooted) when you restart.

but it would be cool if such a feature got added. Maybe even as a peripheral.

Well, a computer can access a directly adjacent computer/turtle like a peripheral and is also able to turn it on or off. If you want a specific program to be executed on startup, you can create a startup file.

Hmm… Maybe a flickering redstone cable should turn on a computer? Or a redstone torch?

I edit the original post to expose better the idea

I think this idea only makes sense. I work for a well known database/server company. In our manufacturing system test department we installed computer controlled opto's that will control the power to a system. We simply issue an opto on command from a xterm and the system begins to power up.

Maybe we just need an "opto" periph. I'm just starting to learn Java or I would make one.

I understand the point, but why not just have the computer on waiting for a command via wireless rednet? When a computer is yielded (waiting for input) it doesn't take any processing power. Added to the fact that if a computer was on at the time of the server/game shutdown or chunk upload, it will automatically turn on on reload/restart, I don't think this would have much use.

Cloudy, on 23 March 2012 - 09:58 AM said:

I understand the point, but why not just have the computer on waiting for a command via wireless rednet? When a computer is yielded (waiting for input) it doesn't take any processing power. Added to the fact that if a computer was on at the time of the server/game shutdown or chunk upload, it will automatically turn on on reload/restart, I don't think this would have much use.

but you have to start the program manualy or modify the startup. With this, all will be hardcoded in the "hardware"

francogp, on 28 March 2012 - 11:53 PM said:

Cloudy, on 23 March 2012 - 09:58 AM said:

I understand the point, but why not just have the computer on waiting for a command via wireless rednet? When a computer is yielded (waiting for input) it doesn't take any processing power. Added to the fact that if a computer was on at the time of the server/game shutdown or chunk upload, it will automatically turn on on reload/restart, I don't think this would have much use.

but you have to start the program manualy or modify the startup. With this, all will be hardcoded in the "hardware"

Why is adding a startup file such a big hardship? I doubt a way of waking a computer remotely will be added when people are too lazy to edit one file to run a command.

Cloudy, on 29 March 2012 - 01:02 AM said:

francogp, on 28 March 2012 - 11:53 PM said:

Cloudy, on 23 March 2012 - 09:58 AM said:

I understand the point, but why not just have the computer on waiting for a command via wireless rednet? When a computer is yielded (waiting for input) it doesn't take any processing power. Added to the fact that if a computer was on at the time of the server/game shutdown or chunk upload, it will automatically turn on on reload/restart, I don't think this would have much use.

but you have to start the program manualy or modify the startup. With this, all will be hardcoded in the "hardware"

Why is adding a startup file such a big hardship? I doubt a way of waking a computer remotely will be added when people are too lazy to edit one file to run a command.

I think that Its an "optimization". If you have a PC waiting… threads are created in memory waiting for a msj. If a PC is shutdown, and hardcoded commnad wake it up (turn it on), you will start to use those threads in that moment (not while waiting) optimizing the use or your real pc/server.

francogp, on 29 March 2012 - 01:15 AM said:

Cloudy, on 29 March 2012 - 01:02 AM said:

francogp, on 28 March 2012 - 11:53 PM said:

Cloudy, on 23 March 2012 - 09:58 AM said:

I understand the point, but why not just have the computer on waiting for a command via wireless rednet? When a computer is yielded (waiting for input) it doesn't take any processing power. Added to the fact that if a computer was on at the time of the server/game shutdown or chunk upload, it will automatically turn on on reload/restart, I don't think this would have much use.

but you have to start the program manualy or modify the startup. With this, all will be hardcoded in the "hardware"

Why is adding a startup file such a big hardship? I doubt a way of waking a computer remotely will be added when people are too lazy to edit one file to run a command.

I think that Its an "optimization". If you have a PC waiting… threads are created in memory waiting for a msj. If a PC is shutdown, and hardcoded commnad wake it up (turn it on), you will start to use those threads in that moment (not while waiting) optimizing the use or your real pc/server.

When a computer is waiting for an event, it is not using up any processing power at all and it is taking up a nominal amount of memory. If you go out of chunk range too, the threads should get unloaded (although they admittedly don't in the current version, even on computer shutdown).

However, I was just voicing my viewpoint; dan may decide to add it, but I think it's unlikely.

Like the idea! I want it too