i have just started working for a school as a ICT technichan .. basicly the school are allowing me to install Bonic on all the computer that i see fit.. the computers range from 733MhZ to Core2 Duo's. basily what im asking is the WU based on account or Computer ? if its account how many Wu would i be alowed to downlod as there is about 300+ Computers on Campus ...

with thanks

---

Limits per CPU (up to 4, I believe) is 100 units.

I also suggest trying to install Chicken's application on as many as possible.

Good luck, and have fun!

---

My movie https://vimeo.com/manage/videos/502242

i have just started working for a school as a ICT technichan .. basicly the school are allowing me to install Bonic on all the computer that i see fit.. the computers range from 733MhZ to Core2 Duo's. basily what im asking is the WU based on account or Computer ? if its account how many Wu would i be alowed to downlod as there is about 300+ Computers on Campus ...

with thanks

The WU limit is per computer, so you'll have no problems.

More particularly, the limit is per CPU core, at least for the first few cores (4? - need to check), so your Core 2s will be allowed double.

Make sure your school's internet bandwidth can stand the strain, and you're not paying by the gigabyte - each WU is about 1/3 of a megabyte to download.

You'll want to install BOINC as a service, of course, and I would invest in a copy of BoincView or similar, so you can monitor any rogue ones remotely from the back office - but good on you - bring them on!

A warning about using optimized clients. This requires a hands on approach, as well as keeping track of changes at the project. Although they process work much faster, Boinc wont be able to do auto-update when a new client is released, but this is not very frequent occurance.

Good luck with all these systems. Happy crunching.

A warning about using optimized clients. This requires a hands on approach, as well as keeping track of changes at the project. Although they process work much faster, Boinc wont be able to do auto-update when a new client is released, but this is not very frequent occurance.

Good luck with all these systems. Happy crunching.

Hopefully he is using an image or deploying through AD so the updates won't be too bad.

---

Fear will keep the local systems in line. Fear of this battle station. - Grand Moff Tarkin

A warning about using optimized clients. This requires a hands on approach, as well as keeping track of changes at the project. Although they process work much faster, Boinc wont be able to do auto-update when a new client is released, but this is not very frequent occurance.

Good luck with all these systems. Happy crunching.

Hopefully he is using an image or deploying through AD so the updates won't be too bad.

will be deployed VIA AD to start with then added to the Ghost Image. the schools bandwith isnt a problem were on a 100Mb's line with No Bandwith limit (very nice) as we are triling some exchange stuff for BT. (were located in the UK) im going to have to play with the Opmised client. have been using it at home with no problems. i know about it haveing to beinstalled as a service (again dose this at home) i havent had any experiance with the remote connection tho. can some on explain/post a link ?

thanks

matt

---

... i havent had any experiance with the remote connection tho. can some on explain/post a link ?

As you might have guessed, I use BoincView from amanheis.de - other people will chip in with other suggestions, I'm sure.

To enable remote management, you need:

* a file called 'remote_hosts.cfg' in the BOINC directory of each workstation you're going to manage. This file just contains the name (or IP address) of the management machine you're going to run BoincView etc. on
* to modify/replace the existing file called 'gui_rpc_auth.cfg' which you'll find again in the BOINC directory of the workstations. This file contains a password - currently 32 random letter/numbers. You'll find it much easier if (a) it's simpler, and (b) it's the same on all machines. Remember this password is stored in plain text on each workstation, so it's insecure - don't use anything which would unlock a more important door as well.

Then sit down at your management console at a time when the workstations will be running, and attach yourself to each of them in turn using the computer's network name and the password (use the 'GUI RPC' option). You'll be able to see WUs in progress and queued, message logs - you can even attach/detach/suspend/abort individual projects/WUs on individual workstations. The only thing you can't do is install optimised apps.

By default, BoincView refreshes the data every 5 seconds, which will be CPU- and network-intensive for your fleet - I suggest you tone it down a bit. And read any advice you can find on the amanheis site about keeping the logs to a manageable size - the message log, in particular, will get huge.