next up previous contents
Next: Running the Source Files Up: Shipping and Installing the Previous: Defining Your Local SNODB

Creating the Directory Structure for SNODB

  The first step is to create the directory structure. Type:

$\sim$/3_06_02/scripts/snodb.perl -dir

This will create the required directory structure and set the proper ownerships[*] for each of them. You should now have 2 directory structures:

1.
The official or test database directory (depending on which was chosen in the snodb.config file) with permission 740.

2.
The server directory. If undefined, it is set by default to be /hepdb/cdsno. It should have the following minimum structure:

/hepdb      
  /cdsno    
    /bad ! dir where the server places bad updates
    /log ! dir where the server logs are written
    /queue ! dir where HEPDB clients place new updates
    /save ! dir where server saves old updates
    /todo ! dir which server scans for new updates

The following top directories will appear if your node is the ``site'' node. (Addition subdirectories are also made but not listed below.) If you wish to test reading and writing to the database using the facilities described in Section 7, set the variable $site_node to your nodename in the file 3_06_02/scripts/snodb_lib/init.pl.

/hepdb      
  /cdsno    
    /write_to_dbase ! Top dir for ascii titles files writes
    /read_from_dbase ! Top dir for ascii titles files reads

On VMS systems, the ACL for the queue directory should be set to allow write access only for the privileged few locals who supply official data to the SNO database.


next up previous contents
Next: Running the Source Files Up: Shipping and Installing the Previous: Defining Your Local SNODB
SNOMAN Account
2/14/1998