Questions and Answers :
Unix/Linux :
How to add another computer on an LAN to your account ?
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 Oct 08 Posts: 2 Credit: 242,224 RAC: 0 |
LAN configuration is a gateway computer with one IP address, other computers are using 192.168.x.x, means they are using NAT(Network Address Translation mechanism). Presently one local computer(tiger is 192.168.0.13) is running boincmgr, boinc_client and one project(hadcm3trans_um). Is it possible to start another boinc_client on another computer on the LAN, let says saturn is 192.169.0.10, using same account that will run another instance of hadcm3trans_um ? Both local computers, that is tiger and saturn, have an user called gilles. |
Send message Joined: 25 Aug 04 Posts: 28 Credit: 6,522,252 RAC: 0 |
....Is it possible to start another boinc_client on another computer on the LAN, let says saturn is 192.169.0.10, using same account that will run another instance of hadcm3trans_um ?.... Sure not a problem. I run copies of BOINC client on different processors and Virtual Machines running both WinXP and Linux. They are all orchestrated from one master Linux process which uses Boinc Manager (plus various shell scripts) to contact and control the individual clients. You just fire up the client process as a daemon/service on each machine. Then you can use the BOINC manager\'s \"Advanced/Select Computer...\" menu option to pick out each processor in turn either by IP address (192.168.1.xxx) or if you are running your own local DNS service on the network you can use its name (myBox.myDomain.myTLD). Andrew |
Send message Joined: 26 Oct 08 Posts: 2 Credit: 242,224 RAC: 0 |
in Message 35428 You just fire up the client process as a daemon/service on each machine Thanks for the help. starting boinc_client on second computer does not work. hum, may be i have a more basic problem. On the second computer, i have the following error. $ cd /var/lib/boinc $ boinc_client Another instance of BOINC is running here are the steps a) on the first computer under fedora 9 distribution, i have install package boinc-client-6.2.15-1.20080818svn.fc9.i386 boinc-manager-6.2.15-1.20080818svn.fc9.i386 easy instruction steps being missing for setup on linux, i endup searching around for help at http://boinc.berkeley.edu/wiki/Installing_on_Linux after which using instruction in paragraph, Optional setup hints. At that point the file /var/lib/boinc/gui_rpc_auth.cfg was available for making the symbolic link(ln -s). Using boincmgr utility, I succeed to attach to climatprediction and it started computing first b) on second computer, still under fedora 9 distribution, i have install package boinc-client-6.2.15-1.20080818svn.fc9.i386 boinc-manager-6.2.15-1.20080818svn.fc9.i386 using http://boinc.berkeley.edu/wiki/Installing_on_Linux under paragraph, Optional setup hints step 7 and step 8 can not be done, cause the file /var/lib/boinc/gui_rpc_auth.cfg is not created by any of the previous packages. That is, boinc-client and boinc-manager. question, should the file had being install ? how to create that file ? remember that following command return with error on the second computer $ boinc_client Another instance of BOINC is running |
Send message Joined: 25 Aug 04 Posts: 28 Credit: 6,522,252 RAC: 0 |
...the file You can set the contents of gui_rpc_auth.cfg to be any password you wish using the text editor of your choice. I leave it empty on my network as my firewall blocks any external access to the BOINC interprocess control port (#31415) for all kit running BOINC. I am running 64bit BOINC from the hard linked Berkeley installer under openSUSE 11.0, however you seem to getting 32 bit packages from the repositories so -- http://boincdl.ssl.berkeley.edu/dl/boinc_6.2.15_i686-pc-linux-gnu.sh -- should do. I run this way because it avoids any dependencies and because I want to control where everything is placed, as I have the file structures of the BOINC installations on each machine mounted back into a central BOINC location for ease of management and backup. $ boinc_client Hmm, it looks as if the Fedora installer has set up boinc-client to be run automatically as a daemon as part of the boot process. In that case you should be able to use boinc-manager to talk to it after setting up the gui_rpc_auth.cfg file. Andrew |
©2024 climateprediction.net