On Wed, Nov 22, 2006 at 12:34:29AM +0900, Thomas Nitsche wrote:
> remote access doesn't work for me. Anyone got this up an running? I did 
> something like:
> 
> fastri-server -a 192.168.100.0/24 -s 192.168.100.163
                                   ====================
> Looking for Ring server...
> No Ring server found, starting my own.
> $ fastri-server 0.0.1 (FastRI 0.2.0) listening on 
> druby://192.168.100.163:35800
> ACL:
> deny  all
> allow 127.0.0.1
> allow 192.168.100.0/24
> 
> Local access works just fine, but from remote I got:
> $ fri -s 192.168.100.163 Array
         =================
> Couldn't initialize DRb and locate the Ring server.
> 

The address given to  fri -s ADDR  is not the address of the server (that one
is autodiscovered using the Ring), but the address the local DRb service must
bind to (in short, fri also exports a DRb service that will be used by the
remote fastri-server to tell fri where it is).

So, if your server is  192.168.100.163  and your client is running on
192.168.100.164, you'd have to do

(in 192.168.100.163)
$ fastri-server -a 192.168.100.0/24 -s 192.168.100.163

(in 192.168.100.164)
$ fri -s 192.168.100.164  Array

or

$ export FASTRI_ADDR=192.168.100.164
$ fri Array


I'm revisiting that code to see if I can make 'fri Array' work without
specifying the local address, but for the time being the above should work.

-- 
Mauricio Fernandez  -   http://eigenclass.org   -  singular Ruby