VI.c Adding alternate directory trees ------------------------------------- Normally, only files and directories with null device specifications in their path names are accepted by the server for display. If a device specification is part of the client-supplied filespec, it must specify the Gopher data directory device. On occasion, there might be a need to have the server access files or directories outside the base gopher data directory. There are two ways to do this. First, the GOPHER_DATADIR logical, or the logical device named in the DataDirectory specification of the configuration file, may be defined as a search list. This has the benefit of being totally transparent to the server, simply adding additional files to the root directory. Subdirectories may become problematic, however, due to DIGITAL acknowledged problems with search lists. From the OpenVMS Database on DSNLINK: "OPENIN, DNF, NOSUCHFILE Errors Using Search List Logicals For DIRECTORY" "When referencing a directory using a search list of rooted directories, ensure that the specified directory exists in all of the directory roots in the search list." and ["Overview of Search List Logicals"] "Access to the components of a searchlist are transparent only if all components have the same access (protections, existence). If the searchlist components are defined with different characteristics, command execution can become inconsistent." An alternative is to create additional logical devices pointing to these additional directory trees. Name these additional logical devices such that they begin with the same text as the configured DataDirectory device. For example, if your configured DataDirectory is "GOPHER_ROOT:[000000]", then any number of logical devices of the form GOPHER_ROOTx, where x can be any additional text, will be honored by the server. Extra-long logical device names, like GOPHER_ROOT_THIS_ONE_IS_A_REALLY_LONG_ONE, might require continuation of Path= specifications which use them. .