One cache / work scheduler with several remote clients attached to it could make BOINC available for more machines, for example

- diskless work stations (pure terminal server clients)

- limited internet firewalls that don't allow 2 connects with the same account

The centralized cache is plausible at some point in the distant future, but the centralized work scheduler is not likely at all.

A centralized cache system was considered, and it would have to be almost a full server, and there would be other complications. For example, the host that does the work is recorded, and must match the host to which the work was sent as an anti cheating mechanism.

---

BOINC WIKI

One cache / work scheduler with several remote clients attached to it could make BOINC available for more machines, for example

- diskless work stations (pure terminal server clients)

- limited internet firewalls that don't allow 2 connects with the same account

Hello pOttO!

I have only one machine at my command, but I know, that you can install BOINC as a service, and get rid of the manager on this machines. AFAIK you cen even start Boinc itself afterwards from a command line window if you insist.

The capability to control a farm through the manager is already build in (lot's of people use it this way), but I've heard , that BoincView should be the more appropriate GUI for that task.

Happy crunching!

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

1.) smokin command line client that can proxy in to the boinc manager that is not necessarily on the same machine similar to the way the seti_classic was arranged.

2.) naturally then the boinc manager would need to support multiple remote worker clients for pharming ;D

I have a lot of computing power at my disposal if i can keep things light on the host machines.