Two question (and a third theoric consideration) :

1. One of the machines on which I'm running BOINC is a headless Linux server. The problem is : BOINC is listening for incomming connection on Localhost (127.0.0.1:1043), not on the local network (192.168.0.:1043). So now, if I want to remotely control the BOINC client, I have to open a SSH tunnel (ssh -L1043:127.0.0.1:1043 192.168.0.2), I cannot connect directly from BOINC Manager.
   
   
   
   • Is it possible to force BOINC to listen on both localhost AND eth0 interfaces ?
     

   
   
   

2. I plan soon to install the BOINC client on a work station that normally runs linux, but occasionnally is switched to Windows for gaming purpose (the games are mostly point'n'click adventure games, so performance hit isn't a issue).
   
   
   
   
   • If I install all clients and copy data files in the same directory on a partition that can be accessed by both OSes (like a FAT32 partition), when I start BOINC/Win32 will it be able to pick up work where BOINC/linux_x86 left ? Or will all data get corrupted due to some obscure difference between the clients ?
     

   
   
   

3. Bonus question : On a completly theorical point of view (I don't have the intention to do it) can two (or more) concurrent instances of BOINC run from the same directeroy and nicely alternate, each one running a different job that the other isn't running ? (could be useful in a farm of diskless servers) Or will it result in massive corruption ?
   

I know that most of this answer could be found by looking at the source, but I'm just lazy,,, :-P

---

1) Try creating a remote_hosts.cfg file on the headless host.

2) Most likely differences in the windows and *nix applications will cause problems.

3) It will make a mess.

---

BOINC WIKI

BOINCing since 2002/12/8

1) Try creating a remote_hosts.cfg file on the headless host.

Found option : -allow_remote_gui_rpc
Which was hidden on my help screen due to weird world warp on my terminal.
It binds to any incoming trafic (ie: that passes the firewall) : 0.0.0.0:1043
eveyrthing runs smoothly now.

---