Thanks, it works now: [EMAIL PROTECTED]:/export/work/globus-4.0.5> globus-rls-cli query rli lfn whatever rlsn://lysine whatever: rlsn://lysine.umiacs.umd.edu:39281
So, I ran that admin command with the lowercase (-a), stopped/started the RLS server, and that seemed to do the trick. My configuration file doesn't seem to be altered, though; how is it that it had a "permanent" effect? I don't want this to stop working all of a sudden. Thanks, Adam On Feb 11, 2008 2:27 PM, Shishir S. Bharathi <[EMAIL PROTECTED]> wrote: > Adam, > > > 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 > > > > So, why doesn't the RLI know about the LFN? For reference, here's my > > config: > > You will also need to configure the lrc component of the server to send > updates to the rli component of the server. Even with a single rls > installation, this is not setup automatically. > > $globus-rls-admin -[a/A] rli lrc > > In your case, > $globus-rls-admin -[a/A] rlsn://lysine rlsn://lysine > > Use -a if you are performing "list" updates (suitable for smaller > datasets) or -A to perform "bloomfilter" updates (for larger datasets). > The rli must be appropriately configured to receive "list" or > "bloomfilter" updates, controlled by the "rli_bloomfilter" parameter in > the configuration. > > Refer to the documentation for details on these modes. > > > By the way, aside from the command reference page, are there example of > > using RLS or globus-rls-cli anywhere? > Probably not. > > Rgds, > Shishir > > -- > Shishir S. Bharathi > USC Information Sciences Institute > 4676 Admiralty Way, Suite 1001 > Marina del Rey, CA 90292 >
