Laserfiche WebLink
CRDSS_VERSION = 1.0.1 <br />The variables that are defined in this file can be used by many applications to locate CRDSS files. <br />Note that the file syntax allows reference to previously defined variables. Such a configuration file <br />allows users and developers to use "local" copies of files during testing and development rather than <br />automatically using the system files. This type of file has been used by RTi to manage large <br />software projects using a single controlling file (and was originally implemented by the National <br />Weather Service for their Interactive Forecast Program development). <br />The definitions in the global configuration file will be superseded by definitions specified in the <br />following ways (the highest precedence shown last): <br />(1)Default values hard-coded in the specific application. <br />(2)The users file. This is a hidden file in the user's home directory <br />$HOME/.crdss.cfg <br />that has the same syntax as the global configuration file. <br />(3)The configuration file specified by the environment variable. This file <br />CRDSS_CONFIG <br />has the same configuration as the global configuration file. <br />(4)The variable as defined by an environment variable. For example, the environment <br />variable could be set to if desired. <br />CRDSS /disk1/crdss <br />(5)Specific command-line arguments for applications. For example, applications could parse <br />command-line arguments that have the syntax: <br />-crdssopt CRDSS=/hdisk1/crdss <br />This capability will be reviewed to determine its need and feasibility. <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />Because of the complexity of the CRDSS, it is unlikely that any file structure developed now will be <br />the final file structure. The file structure proposed in the discussion section of this memorandum is <br />given as the initial file structure for the CRDSS. It follows general UNIX software and data storage <br />conventions. <br />Flexibility in the system will be maintained through the use of a global configuration file. Important <br />system variables will be defined and will be accessed by a single lookup routine. A change in file <br />organization (e.g., moving files from one directory to another) will then only require a change in the <br />configuration file and not a recompiling of code. <br />4 <br />A275 05.10.94 1.05-23 Malers <br />