Hi Dave, We think the problem actually stems from the sandboxed permissions of boinc_project and boinc_master when Boinc is installed as a service on Windows. Doing
net localgroup administrators neither boinc_master nor boinc_project were listed. So we added net localgroup administrators boinc_master /add net localgroup administrators boinc_project /add to our install script and things worked fine after a restart. I think it's because each time the wrapper tried to communicate with the client, it didn't have permissions to do so, and would exit; but then the client would see it has a free CPU and would restart the job until we hit the 100 retry maximum. As an administrator, the boinc_* user running the wrapper can properly communicate with the client. We are only running our own project, so I we're not too concerned with the security implications of elevating the privileges of the two boinc_* users. I had tried redownloading the wrappers from the WrapperApp site, but they didn't solve the problem. We also tried using the wrappers that come with the debian7 virtualbox server; those didn't work either. Thanks, Bill _______________________________________________ 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.
