Setting up the Data Directory In each directory of your data hierarchy create a file called menu with one item for each file or directory you want _gn_ to publish. Items in this file have a format like the following: # This is a comment Maintainer=mailto:gnperson@host.edu Name=This description of the file will display on the client Path=0/path/to/dir/file Type=0 Host=YourHost.YourU.edu Port=70 Name=This is a subdirectory Path=1/path/to/dir/subdir Type=1 Host=YourHost.YourU.edu Port=70 Name=This is a remote link Path=0/myfile/path Type=0 Host=MyHost.MyUniv.edu Port=70 The line starting with Maintainer= is optional (and provides information only to HTTP clients). It should contain a reference to the maintainer of this directory like the one above (technically any URL is permissible). The Maintainer line must be the first non-blank and non-comment line in the menu file. There are several things to note about item entries in this file. The Name field must be first, the Path field starts with a _gn_ type (e.g. '0' for a file or '1' for a directory, see the Appendix to this document for more details). It is followed by the path name of the file or directory relative to the top level data directory. The Type, Host, and Port fields are optional for local items, but required for remote links. If they are not present, the Type will be taken from the first character of the Path field and the Host and Path fields will be those specified in config.h (or on the command line of mkcache). In general it is a good idea not include the Host and Port fields for local items. This makes it much easier if at some future time you should wish to move your server to a new host or new port. For more details on the format of menu files see the man page mkcache.1 and the sample menu files in each directory of the source hierarchy. After the menu files have been created you must run the mkcache program to produce a .cache file. This can be done once for each directory or once in the top data directory with the "-r" option to make all the .cache files for the hierarchy. You might want to look at a .cache file to see what it is like. .