The host record shows 4 cores which means this machine should only be getting 24 total tasks ...
The only viable suggestion that came up on the project site is that the user is "spoofing" the number of cores with the CC CONFIG option <ncpus>. Side speculation, the user is setting the value high, getting a surfeit of tasks and then resetting it so that the number looks acceptable on the site when examined. Not sure if you could see this in the server side logs or not ... On May 27, 2010, at 1:09 PM, Travis Desell wrote: > One of our users has appeared to have found a way to get around the workunit > cache limit. I was wondering if there's anything we can do about this. > > milky...@home has an 8 WU per core limit, and for some reason this user: > > http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=171705 > > has around 3000 tasks pending, which shouldn't be possible. > > Is this because of some bug, or malicious use? It really screws up some of > the validation as a lot of those workunits are part of a quorum. > > thanks, > --Travis _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
