CD-ROM Information System

Installing public data at a new site

Installing public data at a new site

Customizing LOOKUP to use your own public data files

If you have installed your own data for Internet access and those files include portions of the public files used by LOOKUP (STF1A, 1C, 3A, 3C), you will naturally want your LOOKUP server to use the local files rather than those at LBL. This is optional, but it will greatly improve efficiency.

LOOKUP uses DBUTIL, which in turn uses files in $STF_INFO_DIR. STF_INFO_DIR is an environment variable specifying where the directory cedr.lbl.gov:/data9/old/parep2/stf/ (or a copy) is locally mounted by NFS. Files in that directory describe data locations in terms of names diskN. For example, the file $STF_INFO_DIR/c90stf1a/ak.loc specifies that the STF1A data for Alaska are in disk130.

When you integrate your public data into the CD-ROM Information System a new unique name diskN (for example disk301) is assigned to each of your local public file systems. (Typically, each diskN corresponds to a CD-ROM.)

To instruct LOOKUP to use your local data, make a local copy of cedr.lbl.gov:/data9/old/parep2/stf/ and modify it as necessary. For example, change ak.loc to point to disk301 instead of disk130. Then change the environment variable STF_INFO_DIR to point to the directory containing your locally modified files.

If your data become temporarily unavailable, temporarily restore STF_INFO_DIR to its original value to obtain data from the standard remote locations.


http://parep2.lbl.gov/mpub/cdrom/doc/install/lookup_custom.html 9/28/94
dwmerrill@lbl.gov