PDA

View Full Version : Remote Hosts File



IronBits
10-02-2005, 03:17 AM
From BOINCWiki

This is a file that is located in the BOINC Directory on the Participant's Computer that allows, if present, one or more other computers to control the BOINC Daemon on this computer.

The computer to be monitored has to be enabled through the use of a file named "remote_hosts.cfg" in the BOINC Directory of the BOINC Client Software on the computer that will be monitored.

The file must be in plain text (use "Notepad" or other plain text editor to create the file).

The file must name the remote computer that will be allowed to access this computer's BOINC Daemon.

See the examples of the plain text file and the directory where one of these files is installed.

The computers that can contact and control the BOINC Daemon can be listed by IP Address or "Host Name". The IP Address will always work, where the "Host Name" will only work if your local name server is working.

Note:
If one of the systems using Microsoft Windows® does not seem to allow access via a name in the Remote Hosts File, create a "share" on that machine and see if that corrects the problem. Also, ports 1043 and 31416 must be open in any firewall.

An example file looks like:

EQ-2
192.168.1.100
192.168.1.101
192.168.1.102
192.168.1.103
192.168.1.104
192.168.1.105
192.168.1.106
192.168.1.107
192.168.1.109
192.168.1.109

With one computer being listed by name, the remainder by IP Address.

Note that each remote computer is listed on its own line, the file is plain text, and is named remote_hosts.cfg.

Note:
The BOINC Client Software has to be stopped and restarted for the configuration change to be detected. In other words, you have to stop and restart the BOINC Client Software after adding the file so that the Remote Hosts File is detected.

PCZ
10-02-2005, 07:07 AM
For clarity i will add the following to IB's post

The remote_hosts.cfg will in most cases only need to contain one line.
The IP of the monitoring box .

If boinc is started with the -allow_remote_gui_rpc switch then all hosts will be allowed access regardless of the remote_hosts.cfg file.

I read quite a few threads about this and in nearly all cases folks were using the
-allow_remote_gui_rpc switch in combination with remote_hosts.cfg files.

Do not do this as it nullifies any restriction imposed by the remote_hosts.cfg file.