Originally posted by: mondobyte
Apparently once distributed, there is little or no direct control of the client possible from a remote computer. It should be possible to uninstall the client and re-install the client with changed parameters without much effort. I believe that I can also use a script to restrict access to the folder from the prying of network users.
BOINC has excellent remote control-capabilities, either by using the included BOINC Manager, but in this you can only select one computer at once, or other tools like BoincView.
To enable remote access, you need to add a file to BOINC-dir, remote_hosts.cfg. On each line of this text-file, add a computer-name or ip-address of a remote computer you will enable remote access from. So, just add the name and/or ip of the computer you're normally using, and all the other installs can be monitored/controlled.
To further guard against malicious users, v5.2.6 is now enforcing the password-function. The password is set in gui_rpc_auth.cfg, so just choose a password of your liking.
In service-install, access-rights on BOINC-directory is automatically set, so only installing user and admins can access the directory at all.
If you're doing some quick tests of BOINC, CPDN isn't really the best choise, since you'll very often get a Sulphur-cycle model, and this takes normally over 2 months to crunch...
For testing it's better to use Einstein@home or SETI@Home, both has fairly short wu, stable application, and appart for Seti's Wednesday-outage for backup-purposes is normally up with unlimited work-supply.
Facebook
Twitter