Yes, it's a central thing. I believe that you only have one registry peers file to point your client at.
If your client cannot read: http://www.accessgrid.org/registry/peers.txt or if the BridgeRegistry processes on all the machines listed within this peers file are down (very unlikely!), then you won't receive any bridges. My guess is that the above website is down (it's slow at the best of times). I don't think there's any way round this for now. But presumably your client is hanging on startup? At least try connecting to the venueserver - maybe you'll be able to navigate to a bridgeserver from there? Cheers, Ben. _____ From: owner-ag-t...@mcs.anl.gov [mailto:owner-ag-t...@mcs.anl.gov] On Behalf Of Dean W. Nobles Sent: 18 December 2007 17:10 To: ag-us...@mcs.anl.gov; ag-t...@mcs.anl.gov Subject: [AG-TECH] Bridge Registry I'm not seeing any bridges (for unicast) in my 3.1 Venue Client. Does anyone know if the bridge registry is a central thing that may be hammered or is it local to my AG node? --dean
