Would this be useful, or even possible...?
Take a box and have a website on it. We'll call this [H]orde Borg Monitoring Server.
Have a client program (invisible service) which is installed on the borgs. We'll call this [H]orde Borg Client.
This client sends to the server once an hour:
-the WU the borg is working on
-the percentage the WU's is complete
The client would have a config file, containing the computer name (auto pulls computer name), folding user name. This will allow us to tell which borg is what, and the user name would sort things out on the server.
- User Name
- Borg 1
The server would also track when the last update was received. If an update has not been received in ~6 hours, the server flags this boxen as down. We would need the ability to remove boxen as they change ect.
Could add in basic PPD action, my thinking is this is primarily used for making sure the borgs are all working. If a borg is not working, you have the computer name to help track the sucker down.
Problems:
The client program would need to know where the files are located (different people put files in different places ect.).
People turning off borgs. --- Have server do historical tracking, on day 1 server received 3 records, day 2 none, but on day 3 got 4 records (this means the borg is still working, computer just off on day 2)
Specs:
Client must be 100% stable
Send tiny amount of information (what, 50-100 bytes ain't gonna take much)
Install as a clean service (adds line item to services menu)
Not send first update after system start up for 1 hour
LAN based basically, just don't deal with modem
I think EM3 and alike will do these basic actions, I'm just thinking of an ultra light version invisible to the borge.
Thoughts? Good/No Good? Will help/Will not help? More stats of some type, cool!
If you borged a buddies machine, and no updates for a few days make an excuse to stop by their place...
edit: since I'll get yelled at anyways... any use of [H] here is joking. won't label anything [H]
Take a box and have a website on it. We'll call this [H]orde Borg Monitoring Server.
Have a client program (invisible service) which is installed on the borgs. We'll call this [H]orde Borg Client.
This client sends to the server once an hour:
-the WU the borg is working on
-the percentage the WU's is complete
The client would have a config file, containing the computer name (auto pulls computer name), folding user name. This will allow us to tell which borg is what, and the user name would sort things out on the server.
- User Name
- Borg 1
The server would also track when the last update was received. If an update has not been received in ~6 hours, the server flags this boxen as down. We would need the ability to remove boxen as they change ect.
Could add in basic PPD action, my thinking is this is primarily used for making sure the borgs are all working. If a borg is not working, you have the computer name to help track the sucker down.
Problems:
The client program would need to know where the files are located (different people put files in different places ect.).
People turning off borgs. --- Have server do historical tracking, on day 1 server received 3 records, day 2 none, but on day 3 got 4 records (this means the borg is still working, computer just off on day 2)
Specs:
Client must be 100% stable
Send tiny amount of information (what, 50-100 bytes ain't gonna take much)
Install as a clean service (adds line item to services menu)
Not send first update after system start up for 1 hour
LAN based basically, just don't deal with modem
I think EM3 and alike will do these basic actions, I'm just thinking of an ultra light version invisible to the borge.
Thoughts? Good/No Good? Will help/Will not help? More stats of some type, cool!
If you borged a buddies machine, and no updates for a few days make an excuse to stop by their place...
edit: since I'll get yelled at anyways... any use of [H] here is joking. won't label anything [H]