Hi Rob, Your scenario sounds appropriate for RLS. And, yes, it's reasonable to > start off with a single RLS installation. And if you write your client > software (or use DRS) to query the "RLI" first and then the "LRC" based > on the results returned by the RLI, you can easily extend your > configuration in the future by setting up additional LRCs and sending > their index "updates" to the RLI. >
I'm trying to do as you indicated here -- I'd like to make queries to the RLI first. Here's what I did as a test: globus-rls-cli create whatever /tmp/whatever rlsn://lysine globus-rls-cli add whatever /opt/whatever rlsn://lysine [EMAIL PROTECTED]:/export/work/globus-4.0.5> globus-rls-cli query rli lfn whatever rlsn://lysine globus_rls_client: LFN doesn't exist: whatever [EMAIL PROTECTED]:/export/work/globus-4.0.5> globus-rls-cli query lrc lfn whatever rlsn://lysine whatever: /opt/whatever whatever: /tmp/whatever So, why doesn't the RLI know about the LFN? For reference, here's my config: # Database connection options db_user gt4admin db_pwd *********** odbcini /export/work/globus-4.0.5/var/odbc.ini update_immediate true # Propagate changes to RLI quickly # LRC options lrc_server true lrc_dbname lrc1000 # RLI options rli_server true # Indicates this is an RLI server rli_dbname rli1000 # mysql-database-name By the way, aside from the command reference page, are there example of using RLS or globus-rls-cli anywhere? Thanks in advance. Adam
