I've got a fine BOINCing machine which is soon to disappear into the depths of a secure area, with no internet access. Anybody got any idea how to keep it happily processing WU's?
If it's got no network access/internet access, it's near impossible to keep it crunching. Mostly because WUs downloaded to the machine are registered to that machine.
You can set up a "dummy" machine (w. internet access) that makes the work transfers, then stop the client there, transfer the whole BOINC directory to the other machine, let the work collected crunch there, then transfer the BOINC directory back to the internet machine, start the client there and update the projects to report the results and get new work.
The exact procedure depends on the OS. With some clients there is also a way to manually start a benchmark run, so the powerful machine wouldn't have to live with the presumingly poorer benchmark results from the dummy one.
If the internet machine will crunch BOINC by itself, you can set up the "dummy" as a VMWare virtual machine, on Linux it will be enough to use a different "BOINC" directory, on Windows it might be best to install another BOINC client as a different user and into a different directory than the default one (Program FilesBOINC).
I need a lateral thought
)
If it's got no network access/internet access, it's near impossible to keep it crunching. Mostly because WUs downloaded to the machine are registered to that machine.
You can set up a "dummy"
)
You can set up a "dummy" machine (w. internet access) that makes the work transfers, then stop the client there, transfer the whole BOINC directory to the other machine, let the work collected crunch there, then transfer the BOINC directory back to the internet machine, start the client there and update the projects to report the results and get new work.
The exact procedure depends on the OS. With some clients there is also a way to manually start a benchmark run, so the powerful machine wouldn't have to live with the presumingly poorer benchmark results from the dummy one.
If the internet machine will crunch BOINC by itself, you can set up the "dummy" as a VMWare virtual machine, on Linux it will be enough to use a different "BOINC" directory, on Windows it might be best to install another BOINC client as a different user and into a different directory than the default one (Program FilesBOINC).
BM
BM
Some good ideas there.
)
Some good ideas there. Thanks!
I'll pull out the network cable over the weekend and see if I can simulate the environment.