For a non service, one can allow remote gui access by haveing boincmgr pass the command as in

boincmgr /b --allow_remote_gui_rpc

I cannot make this work. All I get is the error message "Unknown long option 'allow_remote_gui_rpc"

I replaced /b with --boincargs but same problem

Anyway, here is boincmgr options:



When I run the above all I get is "unknown long option" for an error message and boinc does not start as shown here:
http://swri.info/images/gui_rpc_error.PNG

Looking thru http://wcg.wikia.com/wiki/Special_startup_instructions it seems there is a lot left out. Since that is wcg, maybe there could be just one place for info about starting up boinc. Since boincview is not up anymore, I am back to google and wcg showed up first. Note the following line in the above wcg wiki:

To add special commands and still start it minimized to the system tray becomes "C:\PROGRAM FILES\BOINC\BOINCmgr.exe" "/s /b, --boincarg" 

That is not correct as /b and --boincargs are different ways to specify that commands to boinc follow. They should not be used in the same phrase. I also tried quotes about the arguments but never got the command passed to BM 6.5.0. Maybe there is some combination of quotes pass the string arg in but I cant make it work. I know this should work as this is what I used in linux but boinc_client is not the same as boincmgr

..TIA..

You may want to use boinccmd (the BOINC Command Tool) instead.

---

You have to use boinc.exe not boincmgr.exe for --allow_remote_gui_rpc, but if you set up the gui_rpc_auth.cfg and remote_hosts.cfg files correctly, you don't need that option.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

You have to use boinc.exe not boincmgr.exe for --allow_remote_gui_rpc, but if you set up the gui_rpc_auth.cfg and remote_hosts.cfg files correctly, you don't need that option.

Gruß,
Gundolf

I have trouble with dynamic ip addresses in the remote_hosts.cfg and cant seem to get dns to work. ie: putting a name in remote_hosts.cfg does not always work.

The boincmgr software should be cleaned up to where it does not suggest that /b can be used to pass commands to boinc. That is another problem however.

You have to use boinc.exe not boincmgr.exe for --allow_remote_gui_rpc, but if you set up the gui_rpc_auth.cfg and remote_hosts.cfg files correctly, you don't need that option.

Gruß,
Gundolf

OK - it would seem that boincmgr is not capabile of passing the command --allow_remote_gui_rpc to boinc when it start boinc up. If so, the boincmgr software should not show the " /b, --boincargs " option as that is in error. I suspect that something is wrong and that option is meant to work.

Once bionc starts up, I dont think it is possible to send that --allow command as boinccmd does not support it maybe.

The boincmgr software should be cleaned up to where it does not suggest that /b can be used to pass commands to boinc. That is another problem however.

Which two versions of BOINC are you trying to connect to each other?

---

You may want to use boinccmd (the BOINC Command Tool) instead.

OK, but that communicates with boinc. I have used it to suspend tasking from a temperature monitor program. It does not start up boinc or boincmgr unless I am mistaken



at "[HKLM]SOFTARE/MICROSOFT/WINDOWS/RUN" I have the following key for boincmgr
"c:\Program Files\BOINC\boincmgr.exe" /a /s

exactly like the above, no quote about the "/a /s" and it was put in by the boinc 6.5.0 windows install.

I wanted to add /b --allow_remote_gui_rpc

but it wont work by just adding that phrase and I dont see what I am doing wrong.

OK, starting over. What is it you want to do? Keep tabs on your Linux BOINC from a Windows BOINC or vice versa?

Again the question, which two BOINC versions is this for?

Usually you can do it without the need for the extra command-line reference.
Make sure that in the BOINC (Data) directory of the remote computer there's a remote_hosts.cfg file that holds the IP address or DNS name of the computer you want to do the control with.

The password in the gui_rpc_auth.cfg file needs to be changed to something you want.

Then you can start a new BOINC Manager from the controlling computer, go Advanced view->Advanced->Select computer, fill in the IP address or name and fill in the password, click OK.

It works here for me with two Windows machines, one running 6.4.5, the other 6.5.0. Since the IP address changes around on my router, I put in the DNS name of the controlling machine in the remote_hosts.cfg file of the 'to be controlled' machine. Works without a flaw.

---

It will work without a flaw if you type the local address of the "to be controlled" computer in BOINC manager's Select Computer dialogue on the controlling computer. If you prefer to refer to the "to be controlled" computer by it's DNS name rather than its local address, you'll need to add the name-address pair to your hosts file on the controlling computer, for name to address translation.

The system "to be controlled" must have had boinc started with --allow_remote_gui_rpc or have the ip address or the dns name of the computer that is to do the controlling put into the remote_hosts.cfg file. If the ip is dynamic or the netbios name cannot be looked up then you cannot get access to the system.

This seems to have been a problem known about and a ticket was written 2 years ago and the solution was a documentation fix that was not implemented. I think they wanted to remove the informational message that the "/b" or the "--boincargs" passed commands to boinc. Look here for the ticket http://boinc.berkeley.edu/trac/ticket/196. If it was never implemented (the ability to pass args to boinc.exe) then I can understand changing the documention. However, I looked at the source code and it would appear it should work. I do not have wxwidgets (it was not in the boinc src repository) so I cant step thru the code that dispatches boinc.exe That is assuming I can actually build it in VS2008. I was lucky to be able to open up the win_build solution file and convert without an error.

The following code should have worked, but I dont think that the arguments are getting into the m_strBOINC veriable. If they are, then they are not picked up by the dispatcher which is below.

bool CBOINCGUIApp::OnCmdLineParsed(wxCmdLineParser &parser) {
    // Give default processing (-?, --help and --verbose) the chance to do something.
    wxApp::OnCmdLineParsed(parser);
    parser.Found(wxT("boincargs"), &m_strBOINCArguments);
    if (parser.Found(wxT("autostart"))) {
        m_bBOINCMGRAutoStarted = true;
    }
    if (parser.Found(wxT("systray"))) {
        m_bGUIVisible = false;
    }
    if (parser.Found(wxT("insecure"))) {
        g_use_sandbox = false;
    }
    return true;
}

the following code sets up the string to dispatch boinc.exe and it would appear capable of supplying the --boincargs list assuming that GetArguements pulls out that m_ variable above.

        // Append boinc.exe to the end of the strExecute string and get ready to rock
        strExecute.Printf(
            wxT("\"%s\\boinc.exe\" --redirectio --launched_by_manager %s"),
            wxGetApp().GetRootDirectory().c_str(),
            wxGetApp().GetArguments().c_str()
        );

BeemerBiker, I had a look at the code, and --boincargs is indeed broken. Not only does it not work, it never worked!

I have amended the World Community Grid wiki accordingly.

Just for reference: if BOINC wasn't buggy, the correct syntax would (I think) have been boincmgr /s /b"--allow_remote_gui_rpc"