Over 6500 hosts?

I find it hard to believe!

---

Take a look at my account, you'll see something similar. In my case, some of the computers I've installed R@H on re-image themselves every night. These computers are in labs and the imaging software wipes off any changes students make during the day. . . and it also kills the boinc install. Every day after they are reimaged, the machines have to reattach to the project. They are the same computer, but each can show up as hundreds of 'hosts' in the system.

It's not easy to get around the imaging software. . if we remove the boinc directory from the reimaging, anything installed in that folder will stay. Yes there are ways to lock it down but IT staffs can't spend a lot of time trying to make it perfect since Boinc isn't likely a high priority to their manager :)

---

Take a look at my account, you'll see something similar. In my case, some of the computers I've installed R@H on re-image themselves every night. These computers are in labs and the imaging software wipes off any changes students make during the day. . . and it also kills the boinc install. Every day after they are reimaged, the machines have to reattach to the project. They are the same computer, but each can show up as hundreds of 'hosts' in the system.

It's not easy to get around the imaging software. . if we remove the boinc directory from the reimaging, anything installed in that folder will stay. Yes there are ways to lock it down but IT staffs can't spend a lot of time trying to make it perfect since Boinc isn't likely a high priority to their manager :)

OK, good explaination, thanks. I guess you'd know if he was a cheat of some sort. As long as it's all in good science, I'm happy.

---