On 2/22/10, Mark Pottorff <[email protected]> wrote: > According to the doc, the requirement for GUI RPC password only applies when > you run boinccmd from some other subdirectory or machine. If I can locate > the boinccmd from the same directory as the active core client
The directory you run boinccmd from only matters because it tries to read the password from gui_rpc_auth.cfg in the current directory. If gui_rpc_auth.cfg is not readable because of permissions, it's irrelevant what directory you run boinccmd from; even if you run it from the right place, it will fail to read the file anyway. > and contact > the client via boinccmd rather then GUI RPC over the network, then I'm > expecting boinccmd to be fully functional without the password. > > Are there other undocumented limitations on functionality? I see no mention > of any reduced level of functionality. Either you're allowed, or you're not. With GUI RPCs over localhost, you can *get* almost any information from the client, but you can't modify anything. > I am tinkering with a "BOINC app" that allows monitoring and control of the > client via browser rather then a direct network connection. All interaction > to the client machine is done via BOINC scheduler and "application", so no > direct network connectivity is required (beyond the normal BOINC client-pull > scheduler protocol). How would you like to be able to abort a bad task on > your alpha cluster, or set the debug flags on one of your alpha machines > without having to actually locate the physical machine and run down there to > modify cc_config? ...or detach all of the machines in a school system from a > project, perhaps even uninstall BOINC, all from a website? Sounds like a great idea, but I'd never do it as a "BOINC app" (ie. one that comes from a project, attached to a workunit). It would make a lot of sense for the client (in the future) to stop science apps from doing any network activity, including (or *especially*) localhost TCP connections. -- Nicolas _______________________________________________ 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.
